Ryzom

Nothing I change in the external config file seems to matter when I start the game. The game is stuck in windowed mode and when I get to the char select screen (I assume thats what it is) all I see is a giant spinning question mark in the middle of the screen, and everything else is off the edges of the screen.

I've read through this board, and many others, and none of the given suggestions do ANYTHING. I have a Nvidia Gefore4 64mb with the latest drivers.

This sucks cause I want to play this damn game, and I spent all the time downloading it... but at this point I'm ready to just delete the f'n thing

Finally got the display problems straightened out... but now I get the following error when I select my character and press "Play." This game is just one damn problem after another.....


A failed assertion occurs
ProcName: client_ryzom_rd.exe
Date: 2004/11/17 19:26:25
File: R:\code\nel\src\3d\driver\direct3d\driver_direct3d.cpp
Line: 2167
FuncName: <Unknown>
Reason: "0"
-------------------------------

Log with no filter:
-------------------------------
2004/11/17 19:26:20 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:20 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:20 client_ryzom_rd.exe DBG 2220 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2004/11/17 19:26:20 client_ryzom_rd.exe DBG 2220 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2004/11/17 19:26:20 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:21 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:22 client_ryzom_rd.exe WRN 2220 sound_manager.cpp 689 : Sound 'specie_but_over' not found !
2004/11/17 19:26:22 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:23 client_ryzom_rd.exe WRN 2220 sound_manager.cpp 689 : Sound 'specie_but_over' not found !
2004/11/17 19:26:23 client_ryzom_rd.exe WRN 2220 sound_manager.cpp 689 : Sound 'specie_but_over' not found !
2004/11/17 19:26:23 client_ryzom_rd.exe WRN 2220 sound_manager.cpp 689 : Sound 'specie_but_over' not found !
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:23 client_ryzom_rd.exe WRN 2220 sound_manager.cpp 689 : Sound 'specie_but_over' not found !
2004/11/17 19:26:23 client_ryzom_rd.exe WRN 2220 sound_manager.cpp 689 : Sound 'specie_but_over' not found !
2004/11/17 19:26:23 client_ryzom_rd.exe INF 2220 ctrl_base_button.cpp 259 : clicked on ui utgame:charsel lay_but
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2004/11/17 19:26:23 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 complex_source.cpp 516 : CS : Chaining to sound ___padchimes
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 complex_source.cpp 526 : Seting event for sound ___padchimes in 1466 millisec (XFade = 1465).
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 connection.cpp 918 : impulseCallBack : CONNECTION:SELECT_CHAR '0' sent.
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 connection.cpp 941 : impulseCallBack : CONNECTION:ENTER sent
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 9 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 udp_sock.cpp 174 : LNETL0: Socket 104 received 42 bytes from peer 38.117.236.143:47851 (38.117.236.143)
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=179) at level 1 (channel 1)
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=83) at level 1 (channel 1)
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 1), 2 actions (ReceivedAck=126/lastAck=12/nextSentPacket=127)
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 net_manager.cpp 243 : impulseCallBack : Received CONNECTION:USER_CHAR
2004/11/17 19:26:24 client_ryzom_rd.exe DBG 2220 net_manager.cpp 265 : <impulseUserChar> pos : 1502.732071 -6649.728316 0.000000 heading : 1.050470
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 net_manager.cpp 301 : impulseCallBack : Received CONNECTION:READY
2004/11/17 19:26:24 client_ryzom_rd.exe INF 2220 connection.cpp 532 : impulseCallBack : received serverReceivedReady
-------------------------------
User Crash Callback:
-------------------------------
UserId: 184900
ShardId: 107
No user entity informations
ViewPosition: 0.00 0.00 0.00
Time in game: 0h 56min 32sec
LocalTime: 2004/11/17 19:26:25
ServerTick: 48729609
ConnectState: Connected
LocalAddress: :1262 (192.168.1.102)
Language: English
ClientVersion: 1.1.0.728
PatchVersion: 00024
Client is online
Memory: 527mB/1023mB
Process Virtual Memory: 228mB
NeL Memory: 0B
OS: Microsoft Windows XP (Build 2600) (5.1 2600)
Processor: Intel(R) Pentium(R) 4 CPU 2.40GHz / x86 Family 15 Model 2 Stepping 4 / GenuineIntel / 2390MHz / 1 Processors found
CPUID: 3febf9ff
HT: YES
CpuMask: 1
NeL3D: Direct3d / nv4_disp.dll / NVIDIA GeForce4 Ti 4200 / \\.\DISPLAY1 / driver version : 6.14.10.6693
3DCard: NVIDIA GeForce4 Ti 4200, version 6.6.9.3
Sound mixer:
Playing sources: 2
Available tracks: 16
Used tracks: 0
Muted sources: 0
Sources waiting for play: 0
HighestPri: 0 / 2
HighPri: 0 / 4
MidPri: 0 / 6
LowPri: 0 / 8
FreeTracks: 16 / 16
Average update time: 0.000397 msec
Average create time: 0.000357 msec
Estimated CPU: 0.001590%%
Sound driver:
FMod Driver
3d hw buffers: 31
2d hw buffers: 32
-------------------------------

Have you tried running in OpenGL mode? Try that by going to the Ryzom Configuration.

Do you have the latest drivers installed for your video card? I would update to the latest, if you're still having problem after trying OpenGL mode.

Thanks for the tip. The game ran good for a minute, then the mouse disappeared and after a minute of slowdown... i crashed again. I am not impressed one bit by this piece of crap. I've never read about/expirienced so many problems with a game. Good job releasing a free two-week trial for a game that doesnt even function properly. Thats a great way to win over the public.

actually i'm more willing to bet that the piece of crap isn't in fact ryzom but it's actually YOUR system, when thousands of ppl aren't having an issue and you are the issue lays with you not the product

here's how you fix 99% of the problems

1 download the latest video card drivers
2 download the lastest sound card drivers
3 download the latest network card drivers
4 download any special ata or raid drivers you need
5 run spyware and adware removal tools (spybot search and destroy and adaware are both free and easy to use)
6 run a virus scan with an up to date dat file (http://housecall.trendmicro.com has a free online scanner)

also knowing what the stats on your system can help as well

onefry wrote:Nothing I change in the external config file seems to matter when I start the game. The game is stuck in windowed mode and when I get to the char select screen (I assume thats what it is) all I see is a giant spinning question mark in the middle of the screen, and everything else is off the edges of the screen.

I've read through this board, and many others, and none of the given suggestions do ANYTHING. I have a Nvidia Gefore4 64mb with the latest drivers.

This sucks cause I want to play this damn game, and I spent all the time downloading it... but at this point I'm ready to just delete the f'n thing

If you have an Nvidia card, pick DirecrX in the configuration in the directory of ryzom...

then it will start in fullscreen...


IF you want to play with opengl fullscreen, start the game in the normal window mode, then pick the gfx configurations in-game, and switch your resolution either up or down, then push aply, the game will then go fullscreen (but in a temp resolution that you choose) when that is done, pick the resolution you want, and pick apply. THIS works for me.

If you see the taskbar at the bottem of your screen simply tab in and out of the game...

minardi wrote:If you have an Nvidia card, pick DirecrX in the configuration in the directory of ryzom...

then it will start in fullscreen...


IF you want to play with opengl fullscreen, start the game in the normal window mode, then pick the gfx configurations in-game, and switch your resolution either up or down, then push aply, the game will then go fullscreen (but in a temp resolution that you choose) when that is done, pick the resolution you want, and pick apply. THIS works for me.

If you see the taskbar at the bottem of your screen simply tab in and out of the game...

actually easier is if you start the game with opengl maximize the window as you're logging in and the game will be full screen

Yes, use the Ryzom configuration tool and set your Driver to OPENGL for Nvidia cards and D3D for ATI based ones. (way it's been since FB) Is you video and motherboard BIOS up to date as well? In the configuration tool make sure you don't just set your resolution and have clicked on fullscreen, make sure that the last number in the res, which is the refresh rate, matches or comes close to the refresh rate that your monitor properties is. It's in advanced display properties for Windows itself. That would likely be why you only saw a question mark. Unless of course you're on a laptop, then you have to make sure you also choose the same resolution as your desktop.

Start out running the game with a lot of the graphics options turned down. A bad one for crashing stuff is the shadows... disable them.

curious...is it a true Geforce 4 or an mx400 flavor of the version. Pretty sure the lack of DirectX9 and the shader pipes would prevent it from working properly.

ok belay my last, I looked at your system specs and saw that it has a Ti4200. so is your card overclocked or soft modded in any way from original form?