Client_ryzom_rd.exe Access Violation

Un petit souci technique ? Pas de problème, il y a sûrement une solution.
Post Reply
armandin
Posts: 6
Joined: Wed Jan 12, 2005 7:43 pm

Re: Client_ryzom_rd.exe Access Violation

Post by armandin »

usulla wrote:amandin la remarque etait pour [url=member.php?u=9263]tianfeng[/url] ;)
sinon [url=member.php?u=9263]tianfeng[/url] tu as pas l'onglet main(hall)? ?
ok.
Toi tu na pas une solution pour moi ?
Top
User avatar
tianfeng
Posts: 550
Joined: Sat Oct 16, 2004 6:26 pm

Re: Client_ryzom_rd.exe Access Violation

Post by tianfeng »

C bon g réussi

je ne m'y connais pas trop en dézippage

je viens de comprendre

c bon, je suis dans le Klient

merci
Top
User avatar
usulla
Posts: 519
Joined: Tue Sep 21, 2004 10:00 am

Re: Client_ryzom_rd.exe Access Violation

Post by usulla »

amandin ta carte graphique est inférieure a celle requise pour ryzom.
La seule chose possible c'est de changer de carte graphique
Top
xtremlan
Posts: 9
Joined: Thu Oct 07, 2004 4:55 pm

Re: Client_ryzom_rd.exe Access Violation

Post by xtremlan »

bonjour, j'ai aussi une acces violation, et j'ai une g-force qui fonctionnai tres bien autrefois avec ryzom, avec les dernier drivers existant, (je precise que ma carte graphique est g-force 4) pourtant il me precise la meme chose... si vous ne faite que booster votre jeu, c'est bien... mais a penser a changer la note de config minimal alors ;) et je precise que je ne suis pas le seule joueur a avoir ce probleme, certain de mes amis ont le meme probleme. j'espere que vous reglera au + vite.
Top
User avatar
usulla
Posts: 519
Joined: Tue Sep 21, 2004 10:00 am

Re: Client_ryzom_rd.exe Access Violation

Post by usulla »

Certaines personnes rencontrent des acces violation qu'ils n'avaient pas avant le patch d'aujourd'hui, un patch correctif pour ce point sera mis en place dès demain.
Top
armandin
Posts: 6
Joined: Wed Jan 12, 2005 7:43 pm

Re: Client_ryzom_rd.exe Access Violation

Post by armandin »

usulla wrote:Certaines personnes rencontrent des acces violation qu'ils n'avaient pas avant le patch d'aujourd'hui, un patch correctif pour ce point sera mis en place dès demain.
Ok , merci
Top
xtremlan
Posts: 9
Joined: Thu Oct 07, 2004 4:55 pm

Re: Client_ryzom_rd.exe Access Violation

Post by xtremlan »

seulement demain?? erf... je vais passer une nuit de solitude... je le sens bien... enfin... c'est deja mieux que rien!! merci!
Top
xtremlan
Posts: 9
Joined: Thu Oct 07, 2004 4:55 pm

Re: Client_ryzom_rd.exe Access Violation

Post by xtremlan »

au fait, voila ce que l'erreur qui apparait, au cas ou vous en auriez besoin ;)

A failed assertion occurs
ProcName: client_ryzom_rd.exe
Date: 2005/01/13 23:27:25
File: R:\code\nel\src\3d\driver\direct3d\driver_direct3d.cpp
Line: 2267
FuncName: <Unknown>
Reason: "0"
-------------------------------

Log with no filter:
-------------------------------
2005/01/13 23:27:20 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:20 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:20 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:20 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:20 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:21 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:21 client_ryzom_rd.exe WRN 3932 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:22 client_ryzom_rd.exe WRN 3932 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2005/01/13 23:27:22 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:23 client_ryzom_rd.exe WRN 3932 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:23 client_ryzom_rd.exe WRN 3932 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2005/01/13 23:27:23 client_ryzom_rd.exe INF 3932 ctrl_base_button.cpp 259 : clicked on ui :o utgame:charsel :p lay_but
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:23 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 connection.cpp 1002 : impulseCallBack : CONNECTION:SELECT_CHAR '0' sent.
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 connection.cpp 1025 : impulseCallBack : CONNECTION:ENTER sent
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 9 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 udp_sock.cpp 174 : LNETL0: Socket 1948 received 42 bytes from peer 213.208.119.194:47851 (213.208.119.194)
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=179) at level 1 (channel 0)
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=83) at level 1 (channel 0)
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 0), 2 actions (ReceivedAck=95/lastAck=-1/nextSentPacket=96)
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 net_manager.cpp 247 : impulseCallBack : Received CONNECTION:USER_CHAR
2005/01/13 23:27:24 client_ryzom_rd.exe DBG 3932 net_manager.cpp 269 : <impulseUserChar> pos : 17125.723813 -32942.383565 -1.862000 heading : 0.215593
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 net_manager.cpp 305 : impulseCallBack : Received CONNECTION:READY
2005/01/13 23:27:24 client_ryzom_rd.exe INF 3932 connection.cpp 598 : impulseCallBack : received serverReceivedReady
-------------------------------
User Crash Callback:
-------------------------------
UserId: 174991
ShardId: 101
No user entity informations
ViewPosition: 0.00 0.00 0.00
Time in game: 12h 7min 20sec
LocalTime: 2005/01/13 23:27:26
ServerTick: 86270709
ConnectState: Connected
LocalAddress: :3963 (192.168.2.3)
Language: Français
ClientVersion: 1.2.0.800
PatchVersion: 00044
Client is online
Memory: 122mB/479mB
Process Virtual Memory: 234mB
NeL Memory: 0B
OS: Microsoft Windows XP (Build 2600) (5.1 2600)
Processor: AMD Athlon(tm) XP 2000+ / x86 Family 6 Model 8 Stepping 1 / AuthenticAMD / 1664MHz / 1 Processors found
CPUID: 383fbff
HT: NO
CpuMask: 1
NeL3D: Direct3d / nv4_disp.dll / NVIDIA GeForce4 MX Integrated GPU / \\.\DISPLAY1 / driver version : 6.14.10.6693
3DCard: NVIDIA GeForce4 MX Integrated GPU, version 6.6.9.3
Sound mixer:
Playing sources: 2
Available tracks: 32
Used tracks: 0
Muted sources: 0
Sources waiting for play: 0
HighestPri: 0 / 2
HighPri: 0 / 4
MidPri: 0 / 6
LowPri: 0 / 8
FreeTracks: 32 / 32
Average update time: 0.000004 msec
Average create time: 0.000577 msec
Estimated CPU: 0.000309%%
Sound driver:
FMod Driver
3d hw buffers: 32
2d hw buffers: 32
-------------------------------

voila.. j'espere que ca sera utile ;)
Top
User avatar
usulla
Posts: 519
Joined: Tue Sep 21, 2004 10:00 am

Re: Client_ryzom_rd.exe Access Violation

Post by usulla »

[url=member.php?u=7962]xtremlan[/url]avec une Nvidia il faut etre en OpenGL et là tu es en D3D. Cela peut être une source d'acces violation.
Top
xtremlan
Posts: 9
Joined: Thu Oct 07, 2004 4:55 pm

Re: Client_ryzom_rd.exe Access Violation

Post by xtremlan »

haaa d'accord... c'est parce que en opengl, le jeu n'avai jamais tourner^^
néanmoins, no probleme en direct 3d depuis plusieur mois... je pense que le nouveau patch a beaucoup trop changer de chose... vu le nombre de bug... ne devriez pas changer les testeur??? sinon moi je suis libre ;)
Top
Post Reply

Return to “Support technique”