probleme lore du chargement de lavatar

Un petit souci technique ? Pas de problème, il y a sûrement une solution.
Post Reply
hulkll
Posts: 4
Joined: Fri Oct 08, 2004 10:01 pm

probleme lore du chargement de lavatar

Post by hulkll »

bonjour voila jessaye de jouer a ryzom et g un probleme lorsque jarrive a la page choix du personage et que je valide g un plentage et une fenetre de ryzom avec lereur suivente


A failed assertion occurs
ProcName: client_ryzom_rd.exe
Date: 2005/03/12 16:58:52
File: R:\code\nel\src\3d\driver\direct3d\driver_direct3d.cpp
Line: 2267
FuncName: <Unknown>
Reason: "0"
-------------------------------

Log with no filter:
-------------------------------
2005/03/12 16:58:45 client_ryzom_rd.exe DBG 3492 string_manager_client.cpp 134 : SM : loading string [219739] as [Arret de Aniro dans 10mn pour une maintenance rapide durant 5mn. Veuillez vous deconnecter svp] in cache
2005/03/12 16:58:45 client_ryzom_rd.exe INF 3492 string_manager_client.cpp 503 : DynString 2252669047 available : [&ZON&Vous êtes dans la région Lac de la Liberté sur le continent Aeden Aqueous.]
2005/03/12 16:58:45 client_ryzom_rd.exe INF 3492 connection.cpp 555 : impulseCallBack : received userChar
2005/03/12 16:58:45 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:45 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:45 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:45 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:45 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:47 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:48 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:48 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:48 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:48 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:48 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:49 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:49 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:49 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:49 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:49 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:50 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:50 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:50 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:50 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:50 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:51 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:51 client_ryzom_rd.exe INF 3492 ctrl_base_button.cpp 259 : clicked on ui :o utgame:charsel :p lay_but
2005/03/12 16:58:51 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:51 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:51 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:52 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 connection.cpp 1002 : impulseCallBack : CONNECTION:SELECT_CHAR '0' sent.
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 connection.cpp 1025 : impulseCallBack : CONNECTION:ENTER sent
2005/03/12 16:58:52 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:52 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:52 client_ryzom_rd.exe DBG 3492 udp_sock.cpp 174 : LNETL0: Socket 1932 received 42 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=179) at level 1 (channel 1)
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=83) at level 1 (channel 1)
2005/03/12 16:58:52 client_ryzom_rd.exe DBG 3492 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 1), 2 actions (ReceivedAck=66/lastAck=4/nextSentPacket=68)
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 net_manager.cpp 279 : impulseCallBack : Received CONNECTION:USER_CHAR
2005/03/12 16:58:52 client_ryzom_rd.exe DBG 3492 net_manager.cpp 301 : <impulseUserChar> pos : 17334.830078 -32893.066406 1.000000 heading : 1.158435
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 net_manager.cpp 337 : impulseCallBack : Received CONNECTION:READY
2005/03/12 16:58:52 client_ryzom_rd.exe INF 3492 connection.cpp 598 : impulseCallBack : received serverReceivedReady
-------------------------------
User Crash Callback:
-------------------------------
UserId: 217657
ShardId: 101
No user entity informations
ViewPosition: 0.00 0.00 0.00
Time in game: 0h 6min 41sec
LocalTime: 2005/03/12 16:58:53
ServerTick: 135387470
ConnectState: Connected
LocalAddress: :1078 (192.168.0.60)
Language: Français
ClientVersion: 1.2.0.800
PatchVersion: 00055
Client is online
Memory: 554mB/1023mB
Process Virtual Memory: 458mB
NeL Memory: 0B
OS: Microsoft Windows XP Service Pack 2 (Build 2600) (5.1 2600)
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz / x86 Family 15 Model 2 Stepping 9 / GenuineIntel / 2827MHz / 1 Processors found
CPUID: bfebfbff
HT: YES
CpuMask: 1
NeL3D: Direct3d / ati2dvag.dll / RADEON 9550 / \\.\DISPLAY1 / driver version : 6.14.10.6512
3DCard: RADEON 9550, version 6.5.1.2
No sound
-------------------------------


g f une verification des fichier reinstaler driver video et direct x et toujour rien

je vous remercie de votre aide

lamort
User avatar
diouxy
Posts: 135
Joined: Tue Feb 01, 2005 7:37 pm

Re: probleme lore du chargement de lavatar

Post by diouxy »

Tu as les derniers drivers ?
hulkll
Posts: 4
Joined: Fri Oct 08, 2004 10:01 pm

Re: probleme lore du chargement de lavatar

Post by hulkll »

diouxy wrote:Tu as les derniers drivers ?




vi et g resolut le probleme en fete il a falu sinplement que je repasse en auto dent le choix de open gl ou direct 3d jeter en direct 3d vu que javer une radeon ati


merci

lamort
Post Reply

Return to “Support technique”