Mnemonic

I made a VR Friendly prop mod for FW-190 A-8, and other warbirds too. https://www.digitalcombatsimulator.com/en/files/3310681/ But yeah, would love to see it as an option in game.

Руль направления влипает в геометрию руля высоты при полной даче левой / правой педали

Investigated a bit further, if joystick to which buttons assigned have a name "F-16 MFD 2" - then above mentioned bug happens, when device is renamed, in my case via TM Cougar MFD drivers, for example to "F-16 MFD 4" - bug disappears. It's very strange but seems that it has to do with some default bindings for Cougar MFDs conflicting? In any way, hope it might be useful for someone.

At extremes of animation for left/right rudder - rudder itself goes through elevator geometry, doesn't look good, very visible especially in VR. It's simple mistake but motion range should be adjusted to avoid it. Happens on every P-47, please fix.

Version Open Beta 2.5.6.54046 Some buttons stopped working in latest Beta when assigned to joystick (works with keyboard shortcuts and clickable in cockpit). Example of button that don't work: - Display mode air to ground - Display mode landing - STEER CMD TACAN - STEER CMD AWL/PCD - STEER CMD VEC Funnily other Display modes and STEER CMD work. Also, what found: - VDI Mode TV - VDI Mode Norm - HSD Mode TID - HSD Mode NAV - HUD Declutter On - HUD Declutter Off - Lights Hook Bypass CARRIER - Lights Hook Bypass FIELD - HUD AWL ILS - HUD AWL ACL - Night Vision Goggles - Night Vision Goggles Gain Down - Night Vision Goggles Gain Up How to reproduce - assign joystick buttons for mentioned actions, click on joystick - nothing happens All joystick buttons successfully recognized in DCS Control Options window, and can be assigned, however pressing one leads to no effect in the Tomcat.

Incredible work Barthek! Thank you very much!

I still have this app on my "old" iPad, any chance for updated Export.lua? Thanks!

Try to turn taxi lights on a Tomcat at night - it's pitch black, and doesn't illuminate at all, you can barely see from external camera when it's on

From the cockpit you can't see anything at all... You can vaguely distinguish if they are on or off, but it doesn't lit up anything...

We don't need to have "baked" reflections meanwhile

Confirm, can be pressed via keybind only on RIO seat.

Great collection of stories, good new (rare) F-14 footage, great overall presentation and spirit. But I loved the stories a lot!

Quite frankly it's too excessive, and doesn't look that good. Looks more like an imprint of a static image and it doesn't move at all when you move your head. Also the same for canopy reflections. Would be nice to have it removable, at least as an option, like it's already done for MFD / canopy reflections in F/A-18, F-16

VR Friendly props for german fighters now available too :) Anton: https://www.digitalcombatsimulator.com/en/files/3310681/ Dora: https://www.digitalcombatsimulator.com/en/files/3310682/ Kurfurst: https://www.digitalcombatsimulator.com/en/files/3310683/

F-14 when used as static, at certain distance shows engine covers only in one eye, the other eye sees lod without theh covers

I have to say this works wonders! Was able to max out most of the settings and still have smooth picture in cockpit. Will play around more. Thanks!

New observation - for late evening / night flying, disable shadows altogether, it improves FPS on the deck when Super Carrier has it's lights on, and at night there are no cockpit shadows anyway.

I wonder why, when ASW has enough frames it works great! Almost undistinguished from native 80 FPS.

No, my goal is to have stable 40 with ASW, which happens if my GPU can output anything between 40 - 80 FPS. I can tolerate it drop below 40, but if that's very occasional. And if I happen to have more than 80 FPS - Oculus ASW automatically shuts down and I have native 80 FPS (ideal conditions). If again I have something heavy going on, I want ASW to catch-up and offload my GPU, so again, no less than 40. I actually like how nicely Oculus ASW works when you give it enough frames to work with. And this is what happens, with the relatively populated carrier (see my included missions) I have 40FPS ASW in a Tomcat while on the deck, taxying around, getting to the cat etc. When I leave the deck - FPS goes up and I have 80, which is nice. I actually don't feel any "jump" because with ASW I also perceive 80 ASW-driven-frames. So smooth all around. Of course if my headset would have much higher input signal resolution, then probably I would need to do something extra. Currently I see a big issue with VRAM. I read your previous comment about having VRAM overbooked is not a problem, well technically yes, drivers do everything for you to optimize the process. So while you are running around the map in Doom or Call of Duty different textures are being loaded to the VRAM and stay there while you are in the area and it's more or less seamless. With DCS a problem becomes more pronounced because there could be situations that to render a single frame you need more VRAM than your GPU has, and next frame is the same. So what heppens driver needs to offload big texture from VRAM to download it again next frame. It becomes a problem when you need to do this operation every frame with large data. While playing on monitor it's still kinda tolerable, you just have less FPS, in the helmet you see double-vision or strange unpleasant stuttering, which is much less acceptable to me. Let's see what next gen GPUs will be, we need large memory on board and fast chips to process all the stuff.

Seems like compute issue, your GPU can’t handle so many lights calculated. I had the same on my 1080 pre-supercarrier when I turn floodlights in F-16 - FPS would go down significantly, same in Tomcat, with 2080 it’s much better +40% of pure compute performance does it’s thing. Crimson_Ghost138 - something to try - set PD less than 1, put it like 0.5 and see if performance will improve. Less pixels for the fragment shader to work with.

Thanks guys! Happy you find this info useful!

Sure, I made a little comparison and you can judge for yourself. All screenshots are made where the effect is most pronounced - when we are looking into the sun. So here is a Hornet cockpit without shadows. So here is a Hornet cockpit with shadows. So here is a Tomcat cockpit without shadows. And Tomcat cockpit with shadows.

What I noticed - main contributing factor to VRAM is PD and Textures

Be careful that you are not in fact capped at 11 at the moment, it could look like 10.5 because every frame driver will offload something from VRAM and put there textures again, and polled value might not reflect it precisely. It's quite high though. Try to put PD below 1, like 0.5 or 0.8, for measurements (drop your VRAM below 9 just to be sure that you have headroom), and then change " screens resolution" to see if that affects VRAM. also for the mirrors (512 every frame) will look better than (1024 not every frame)

And if you use mirrors put “512 every frame” otherwise if it’s not every frame - ASW goes crazy and doesn’t smooth out properly