Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cameni]

One issue is that this version requires restart (will be fixed) before the changes of terrain quality and FOV affect the tile cache size, so this may be what you have experienced.

[ZeosPantera]

I should probably also mention that I have had both a tremendously long period without an app crash (~90minutes driving up a mountain from the shore) and today testing for the terrain load somewhere around 20 or so stopped responding crashes pretty consistently 30 seconds after login. This kept happening until I flew away from that position. Now the crashes are back to a random interval.

What I was looking out when crashes were constant.  http://i.minus.com/iMYVwCYwLoxD6.png http://i.minus.com/iwra4WMDWCTS1.png

[cameni]

Could we get the cache folder? Might check it on 4850 or pass it to AMD, now that it crashes so reliably

[ZeosPantera]

Here you go.  And an image taking you to that Russian test area http://i.minus.com/ibrbzM19JekROo.jpg

[cameni]

The problem is definitely connected to the new Nvidia beta driver, both Anteworld versions don't work any more and exit with the same error :

ERROR: error linking the program sEFBE127F990877C0BA52EB922647F0A8C1CA1B52|sF667327894CF465173DAAE2AD9E3A0CDBA4615EC|s44CE61ED48CBC0EC7C7D1842AF12BAA2AEC32A6A

worked fine with the old driver...

That 304.79 driver is total mess. Seems that Nvidia is trying to revive that one miserable branch of drivers again
I just hope they don't get the idea to WHQL it.

[giucam]

I tried Zeos's cache data and image but my 4850 didn't crash.

Btw, I saw something interesting: i went up in the space and i spawned the cessna. Besides some lighting issues, the model flickered a lot. I then moved the outside camera to look top-down and i saw that the flicker was actually the plane moving back and forth from the right position to, i'd say, ~100 meters below.

Right position:


Wrong position:

[RaikoRaufoss]

That 304.79 driver is total mess. Seems that Nvidia is trying to revive that one miserable branch of drivers again
I just hope they don't get the idea to WHQL it.

That's a shame, I've always had a good experience with Nvidia drivers, but I've only experienced the factory installed Nvidia drivers, 266.58, 296.35, 296.70, and 296.88.

[cameni]

Back from travels, here's a new bug fix patch 0.7.12.3189:

• workaround for NV 304.79 beta driver bug in glsl with switch statement
• fixed termination of the program on GL errors
• fixed precompilation of MSAA shaders when MSAA is disabled
• fixed handling of exif string format (some photos with exif weren't working)
• photos without altitude record now auto-adjust to the ground position

Note that with NV beta drivers 304.79 the program now passes through the initialization phase, but the lighting seems to be severely broken and there may be also other bugs. Since the Nvidia developer forum had been hacked and shut down shortly after I asked for renewal of  developer access there, we can't report these issues there now ...

[alexmdv]

With driver v.301.42 WHQL works correctly.

[cameni]

I tried Zeos's cache data and image but my 4850 didn't crash.

The same for me, I tried the cache and ran around for some time. Nothing happened with UFO; truck flickered wildly but otherwise no crash.

That makes me wonder - Zeos, can you check the loaded modules in your eng.log? Is Fraps listed there? Fraps and similar software hook into other apps and intercept messages, it could be that it interferes somehow even if not used. Or maybe there's another utility ...

Btw, I saw something interesting: i went up in the space and i spawned the cessna. Besides some lighting issues, the model flickered a lot. I then moved the outside camera to look top-down and i saw that the flicker was actually the plane moving back and forth from the right position to, i'd say, ~100 meters below.

Thanks for reporting, it ultimately helped to identify the cause of object flickering, appearing on all vehicles. It was fixed internally.

[giucam]

The same for me, I tried the cache and ran around for some time. Nothing happened with UFO; truck flickered wildly but otherwise no crash.

That makes me wonder - Zeos, can you check the loaded modules in your eng.log? Is Fraps listed there? Fraps and similar software hook into other apps and intercept messages, it could be that it interferes somehow even if not used. Or maybe there's another utility ...

Well, it didn't crash right away but it still did crash after a while, and i don't use fraps. (My plan was to drive the cessna from space to ground, but the crash caught me short after i took those screenshots  )

Thanks for reporting, it ultimately helped to identify the cause of object flickering, appearing on all vehicles. It was fixed internally.

I'm glad i could help

[cameni]

Patch 0.7.12.3191

• grass shadowing (whole blades)
• fixed terrain quality settings to be changeable in runtime without the need to restart
• fixed collision bug (collision mesh not read back correctly occasionally)
• fixed vehicles jerking in motion

Still waiting for Angrypig to finish the shadowing system so it can cover normal distances, If you want to see the shadows now you have to set the shadowmap distance to a low value like 25m.

[hhrhhr]

crash after update. report is automaticaly sended with crashsender.exe.

[cameni]

There seems to be an issue with water rendering, your saved camera is somewhere close to the sea?

[hhrhhr]

after the first crash I removed world.cfg, now there is standart position:
longitude-sun = 143.912231,
latitude-sun = -10.601093,