Fair Haven,

[borg9]

Prior to the patch, I occasionally , very occasional crashed in FH.

Since the patch

I crash when I TP to Fair Haven, has happen on 3 occasions now.

This is a crash to desktop, with a submit report dialog.

I have sound disabled.

I have graphics set to MAX.

I can login again, and move around FH normally.

However, the boardwalk planks, blur and the water shows through in the distance.

I can enter and leave the GH normally, however the HQ look armour on the Guild Apart Caretaker specles on returning to town.

Any clues?

These have only appeared since the patch, and I have made no external software, driver changes.

ATI card (256mb)
P4 3.02
2 gb Ram
Plenty of free disc space.

Ryzom is the only game installed on it.

This machine is my Ryzom box

[sprite]

I seem to remember seeing something about a new email address set up so people can email dump files generated by crashes to the devs... Maybe try that? (sorry, forgot what the addy was...)

[borg9]

I seem to remember seeing something about a new email address set up so people can email dump files generated by crashes to the devs... Maybe try that? (sorry, forgot what the addy was...)

yer say that post, I submit the crash logs anyway. I also notice that the next patch will dump more detailed info to help them track these sort of things down.

It was more of a foot stamp than a plead for help. I have to return to FH everytime I switch jobs or a guildie requires something. So a 1.5hr game could end up beinf a bit like this.

Login in Loria, harvest abit.
Get a request for armour.
TP to FH - crash

Login wait 30 sec + 2 mins for load.
get armour from GH or Packer or craft it.
Die
Spawn at Lorai
Continue to harvest for a bit.
Get ask if I wana go hunting
TP to FH - crash

Login wait 30 sec + 2 mins for load.
Get armour from the only stable I can access now.
Store mats
TP to resting waters.

Fight for a bit.
If I want to return to harvesting later I must go through FH.

Its a pain, but I can live with it.

The crashing, when it didn't before, is just an inconvience.


What I don't like is the graphics messing up!

Kills the imersion if while running though town it looks like the place is flooded or I am passing through a Star Gate(tm)

[sprite]

sounds painful

[kostika]

You might try turning your graphics down. I'm betting the load of the graphics at max is making Ryzom spaz. I know you're fine once you log back in but its jsut something to try.

I use just the average/normal settings and FH still kicks my a$$ with lag.

[sx4rlet]

Since latest patch i have lots of problems with my Ati card too.

Same thing about the bridges and the water shining through in
the distance...

And it gives an error (and crashes) after playing for an hour something
like that...

Sxar

[petej]

Prior to patch 30 I was running my ATI 9800 pro (128M)/ P4 3G/ 512M PC3200 using OGL -I know they recomend D3D but ive always found it to run much smoother. After patch 30 I had 10 access violations before finaly giving up and going to bed , next day another 8 crash's in the morning before speaking to Soulsnatcher on klients. Soulsnatcher asked me to email my nel_debug.dmp file/ login name / character name and slot to dump@nevrax.com which I did , I then switched to D3D mode and hey presto no more access violations

-only trouble is D3D runs in a very jerky manner on my comp with frequent disc access's and realy is almost unplayable for travel through agro areas

Im running with:-
D3D / No sound / Low landscape detail / Normal char detail / Normal Fx detail / Normal (64 mo Vram) Textures -set in ryzom_configuration_rd

and

General= Fullscreen 1024 x 768 85 Hz / Landscape= Landscape Far Clip 600m , Tile Near Clip 50m , Quality 100 , No Micro Vegetation / Characters= Max Polygons 50000 , Max High Def 20 chars , Far Clip 150m / Special Effects= Limitations Max Polygons 10000 , Enable Clouds = Off , Quality 160 , Update Frequency Min, Enable Shadows = On -set in game configuration

-doesnt seem excessive to me

[borg9]

After Yesterdays patch....

No crash in FH.

Not sure what you did wrong the first time with patch 30, but patch 33 fixed it.


Thanks