Coug4r

It depends on the speed. Lower speeds make the ships deviate more.

I'm on a 5800X and the first thing i also noticed was the fps fluctuation.

2.9 still does this.

The world.searchObjects function doesn't return scenery for a very long time now, this used to work. Would be nice if this would be fixed.

Happens in ST and MT. (part of the screen on the left has gone black)

Yeah, saved default view settings (zoom included) are messed up or not loaded. (in the Hornet)

Yes this seems very much fixed! Thanks again!

Thank you!

Awesome! Thank you, thank you, thank you!

There ya go. options.lua

Ok so no AMD/NVidia problem then. I might as well post logs from both versions, there are some differences apart from the CPU-Core/Thread info. For example the entry 'VISUALIZER (Main): cascade shadows init (preset:'default' quality:4 layers:4 size:4096)' doesn't show up in the MT version and there are some other differences. dcs_MT.log dcs_ST.log

Then it might be likely it's a combination of things. Video card perhaps? I'm on a Radeon vid card, Windows 10.

See attached mission. When the SC drops below a certain speed, either commanded by script or directly from the ME, it heads in the opposite direction of where it should go. (speeding up the mission helps, SC is moving at 1 knot) Thank you. SC-Test-001.miz

Still isn't fixed in today's update.

For me this hasn't been fixed (yet).

You could check out Immersive Display Pro from Fly Elise. It seems they still have trial versions to set up a multi monitor-render config properly.

[MT - SP and MP, ST version is fine] First thing i noticed in Marcos' posts is that the area width where the shadows seem to missing is exactly the width of the unused part of the DX surface. Saw the same thing happening here but with different widths. My screenshot: It's like some layer isn't shifted to the proper position. Recording of the issue: My settings: Monitor config is attached. Hope this can be fixed, especially in the pit it's pretty annoying. Thanks QHD-3Monitor[1-4].lua

I seem to be having almost the same issue, will post more details later.

Still no go, still no headtracking

Still no go with the dll.

What the title says. 2.7 (amazing clouds!!) works fine without the headtracker.dll but unfortunately without headtracking. Is this API posted by Wags still valid for DCS 2.7? It still was on 2.6.

Are you using headtracker.dll? That makes 2.7 crash here, without the dll it works but without headtracking obviously. Worked fine on the latest 2.6 version.

If you do it on mission level you could use timer.getTime or timer.getAbsTime and add it to the mission start time and date. Not sure what happens if you'd pause the mission though if that would apply or if that method would be accurate if a missions runs for more than 24 hours

Came across this post while I was trying to do the same thing. Not that it would solve your problem but there are 2 bugs in your code. DCS.getRealTime is a function so you have to use DCS.getRealTime() and getModelTime() lacks the DCS. prefix. It would be nice to have some function to get the actual mission time on server level indeed.

Just don't update :)