Helios1138

btw, I see this both in 2.5.5 and in 2.5.6

there's something wrong with a/b effect between AI aircraft and player-controlled one. it's almost as if each renders the half of the complete effect, one internal and the other one external (flame) this is how it looks on AI viggen: and this is how it looks on player-controlled plane:

thanks!

Is there a VR pilot body already in the module? It's surprisingly hard to get this info on various aircraft while considering which ones to buy...

I just found this thread while looking for the same thing. I wonder if there was any progress in the past 3 years on figuring out how to extend the heat blur past the speed limit. Also, trying to figure out how to increase the speed/frequency of the "shimmering" effect. Does anyone have any useful info?

is there any information about that? is it planned? I know it's an old module, but still...

Ok, scratch that, apparently I simply saved an altered position for myself. THIS ISSUE IS STILL PRESENT. I've bought a few more modules since then and the issue pops up almost everywhere. It's especially obvious in aircraft which have pilot body modeled, so you can roughly see where the pilot's head is supposed to be, and the VR head center point DOES NOT MATCH it. I think this is a very major issue for VR users in many aircraft.

Id it possible to get the developer version somehow?

Really? That's a shame. Why is it even mentioned in the controls setup then?

I see a "LAlt + `" combination in settings to open the console, however it does not seem to be working. I assume there is some sort of debug mode switch/setting that I need to enable somewhere for the console to work?

Yes, now it looks great. Thanks!

Compared it with a photo I took of Su-27 and now I think v1 is actually pretty accurate. The photo is midday end of august, so maybe it should be just a tiny bit brighter in the evening (18:30-18:40).

Can't really see it in v4. Day (well, evening... aka caucasus 30 aug 18:40) version looks about the same as v1, night version looks even dimmer than in v1. I think I'm gonna stick with v1 for now. Otherwise, awesome work!

Is it possible to make a version, where the day a/b is the default DCS one, only the evening/night version is altered?

7 Yes 8 Yes And how can this be achieved? I assume that a lot of these tricks involve manually editing some config files, but I'm not aware of any documentation existing that would describe exactly what I need to do.

It seems that this was fixed a few updates back, so the issue is gone as quietly as it appeared (meaning I did not see anything about this in the changelog), at least for Spitfire. I did not check other aircraft yet. BIGNEWY, can you confirm that this was indeed looked at and fixed and it wasn't just a problem that randomly appeared and then disappeared?

thank you everybody

Oh, so /Saved Games/DCS/ does contain everything? There's nothing in the game directory itself that I need to save?

Is there a list of files that I should manually save if I want to move the game to a different drive or event a different PC so that I would not lose my mods, missions, settings, controls setup, etc. I know that some of the files are stored in "Saved Games", but I assume it's not everything?

Does anybody know if it's possible to: - change the bokeh/depth of field strength? - change the bokeh/DOF focus distance? - enable DOF in F1 cockpit camera mode? - enable DOF in F11 free camera mode? - point F11 camera somewhere other than the direction of movement? so that e.g. the camera keeps moving forward, but I point it sideways? - move the F11 camera with a joystick? it's not really possible to achieve smooth tracking shots with a mouse, but joystick bindings are greyed-out in control settings - disable pilot blacking out/G-effects in F1 camera - disable F1 camera movement restrictions? currently, there is only a small box in which I can move it with num keys (while, for example, in VR I can obviously move my head anywhere inside or outside the cockpit) - save F11, F4 camera movements in a track (as I understand, by default only F1 camera/head movements are saved in a track)? - get back to saved head movements in a track playback? when I start the track, head movements play from the recording, but If I then manually adjust the camera, how to get back to saved movements?

BIGNEWY, any news?

BIGNEWY, thanks for looking into it. Moving the head using the keyboard isn't really convenient in VR since I would have to do this every time after re-centering (and in VR you usually have to do this more than once during flight). I've also checked non-VR mode and it seems that this issue is not present there. Only in VR. By the way, I have since noticed a similar issue in Yak-52. In it, it seems the default head center view has been moved a little bit forward (again, compared to stable version). It is possible that other planes are also affected, hadn't checked them all. I use Oculus Rift CV1. Please let me know if there is any other information I can provide. I did make a couple of screenshots to demonstrate the issue: (screenshots made immediately after re-centering, so I press '5' and then 'F12' to take a screenshot while looking directly ahead) Spitfire (stable) Spitfire (openbeta) Yak-25 (stable) Yak-25 (openbeta)

I've looked through the open-beta changelog here on the forum and didn't find any mention of this (maybe I've missed something?) but in open-beta, the default head position is moved up significantly, so that now I have to tilt my head down to be able to see through the gunsight (or re-center the view while standing up a little, then sit down to lower it to somewhat match the stable version behavior). Is this an intentional change or a bug? I had never sat in a real Spitfire, so obviously I have no idea where the head should be located (for an average-height person) :)