Print

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

[driflysh]

Hello,

after one of the last updates at least the cylindrical view seemed to work so I bought the alpha. Unfortunately this view doesn't work in cockpit view. And spherical still doesn't work in free flight, outside or cockpit view. Some Screens are attached fo cylindrical cockpit, spherical cockpit and spherical free flight. Straight ahead both cockpit views are just black screen. Trees are very small and sometimes "jump" infront of me depending on view direction, only in spherical.

The Issue regarding heaven display seems to be fixed already.

I also just discovered that the sim gets stuck from time to and can be reanimated by right-mouse looking combined with pushing steering buttons...

Log: http://pastebin.com/6ZRQGYLi

Anyway great work up to now!

[cameni]

Cockpits won't work reliably in this mode until they are dynamically tesselated and clipped, since this mode is technically a hack over the linear rasterizer. But the rendering of trees in spherical mode seems to be another bug.

[driflysh]

Oh, that doesn't sound like there'll be a solution for the cockpit view soon. Can I deactivate the cockpit-model? Cause I can live without instruments but flying a helicopter on three 42" screens with this stretched view will render me sick after 30sec...

[cameni]

You can set sim_mode = true in eng.cfg
If you have perf issues after that, you can also press alt+e while in the aircraft, and edit set_fps_position to move the camera in front of the plane.

[driflysh]

sim_mode = true works perfectly! Thank you very much!

Unfortunately that heaven-issue (like a ring in one color, differing in size and angle, starting at the horizon) occured again, but not only in cockpit view and very seldom. But it's ok right now cause I'm only looking at the mountains and trees anyway.

[DivineSense]

Serious startup issues here. Dark star sky is shown, high CPU and program goes unresponsive.
Sometimes the login window is shown without textures. Sometimes it actually starts and is completely fine, maybe 1 in 20 tries works.

I've tried reinstalling Outerra from scratch.

Win64-bit Nvidia gtx660.

Attached my eng.log

Edit: Managed to start it with debug-flag set in eng.cfg.
First I'm getting:
ERROR: (DRV): Buffer performance warning: Buffer object 4 (bound to GL_PIXEL_UNPACK_BUFFER_ARB, usage hint is GL_STREAM_DRAW) is being copied/moved from VIDEO memory to DMA CACHED memory.

Then when the terrain loads:
ERROR: (DRV): Pixel-path performance warning: Pixel transfer is synchronized with 3D rendering.


New Eng-log attached.
Newest Nvidia drivers just cleanly installed (335.23)

[obren]

Hi, guys. I have a startup error, and I presume it's because the latest beta Nvidia driver 337.50, I'm not sure tho. I get the error message, Its something like: Failed to precompile shader, open GL error, failed to link shader program, etc. Anybody has similar issues?

[cameni]

Serious startup issues here. Dark star sky is shown, high CPU and program goes unresponsive.
Sometimes the login window is shown without textures. Sometimes it actually starts and is completely fine, maybe 1 in 20 tries works.

...

Sorry I haven't caught this.
There's one potential problematic module that seems to be injecting into Outerra:

Code: [Select]

C:\Program Files (x86)\DisplayFusion\Hooks\AppHookWIN6032_E500B5BA-2E1F-46A5-A503-6D04045D70A4.dll (Binary Fortress Software, DisplayFusion Hook), version 5.1.1.11

Can you try stopping it before running outerra.exe?

[cameni]

Hi, guys. I have a startup error, and I presume it's because the latest beta Nvidia driver 337.50, I'm not sure tho. I get the error message, Its something like: Failed to precompile shader, open GL error, failed to link shader program, etc. Anybody has similar issues?

We'll check this, but Nvidia beta drivers often break OpenGL stuff, while the subsequent WHQL drivers again behave correctly ...

[2eyed]

Same for me, fatal error at startup:
exception msg:OpenGL error:failed to link shader program
last
RL:MapRender::post@c\_root\srcsvn\eng3x\src\test_frat\maprender.h
pp(401)

[cameni]

It seems to be a bug in the Nvidia beta drivers, access violation inside the driver on one of the shaders. Doesn't report anything else but "internal exception", so it's nothing we can do with it except suggesting to avoid these drivers.

[DivineSense]

Hi!

Yes, I suspected the DisplayFusion Hook, but it's the same with that service turned off...
And I'm running WHQL drivers 335.23, not beta for me.

[cameni]

Did it disappear from the eng.log when you turned it off?

[Levi]

Hi!

Yes, I suspected the DisplayFusion Hook, but it's the same with that service turned off...
And I'm running WHQL drivers 335.23, not beta for me.

Hi! I'm using the same drivers (335.23 WHQL) on my old GeForce GTX 550 TI, and it works perfectly nice for me.

[Foxiol]

The game gave me a "Fatal Error" with drivers 337.50 in Outerra, and there are other issues with other games such as Planetside 2 giving black screens and such. Yesterday it gave me a Blue Screen and my PC rebooted.

I installed the drivers 332.21WHQL and those have no problems at all...no problems with Outerra, no problems with black screens.

I recommend to hold with the 332.21 until Nvidia fixes their drivers.