XCNuse

And this mentality is ruining the fun of today's technology that can be used on aging frames. If it required new systems, it would make more sense to question things; but if you can literally plop a system onto a pylon and it works with literally zero effort... we SHOULD be able to do it. Which exactly what the APKWS system was designed to do. I truly don't understand the people say "no that's unrealistic for what's been designed" when... there are literally this aircraft flying around using these weapons. How is that unrealistic?

I don't have a replay, but can likely easy get one; night mission, enabled TV, put it in IR mode and... white. Solid... blank white. Contrast and brightness knobs had zero effect on the TV. Switching from IR back to TV, still solid white, made no change in brightness; despite before pressing IR mode, the image was solid black (because it was 1AM mission time). For reference this was on the NTTR map.

Shoot, even an IR flare would be a good start; we've already got signal flares, can one be made so it's visible only in IR?

Bump for this. Disabling shadows nearly doubles my FPS at least in VR, but seeing things in cockpit depending on time of day becomes next to impossible due to light reflections. Cockpit only shadows would be a massive FPS booster for a lot of people; but should be an option either way, as they're really the only true shadows that really matter.

Can this be revisited? This is insanely frustrating and without anything informing anyone that it wouldn't work I just had to quit playing because... we didn't know it wouldn't work for me in a Viper.

Sorry for delay, I hardly ever get on this forum. Make sure that you run OTT or the Oculus Debug Tool. I had set mine to 3684. That said, at 1.5PD my 1080Ti was DEFINITELY struggling on a simple mission (was on the F16 cold start Caucasus mission); I was running at the default VR preset. I ended up giving up and going down to 1.3PD for the sake of framerate which brought a lot of it back up to a reasonable amount of ASW usage. Going to up the 1.5PD though really made things incredibly clear, but yeah, my 1080Ti was steamrolling a bit haha

As it stands, Mavericks are fairly broken right now in some form; at least with TGP, that said, without TGP they're pretty fast and easy to use; literally just hud as soi, slew to target area, mav as soi, FOV zoom, and TMS up until the cross collapses on target and launch. Personally I haven't been able to get PRE mode to work once, also because my TGP likes to break every time I try to use it with mavericks onboard. But VIS designation and locking with the HUD is fast and dirty; but it works, and doesn't break... as many things. Mavericks still like to break the steerpoints though because of the current SPI issue which ... knock on wood will be fixed in the coming patch in two weeks.

Can confirm it's also breaking my TGP. Once I load any mavericks onboard and hit A-G, enabling steerpoint autopilot only wants to go straight ahead until I return to Nav mode.... and hit CZ again. Also, more importantly; with Mavericks onboard and nothing being touched, once you reset to CZ on TGP, you can no longer slew the TGP.... at all. It WILL NOT MOVE. Entirely frustrating. Jettisoning the mavericks does not seem to fix the issue either. Viper broken TGP and Mavs.trk

Can you clarify what you mean between "the two?" Not sure I follow. 1070Ti will certainly struggle a bit more, at 1.5PD and the VR default settings I'm fairly positive even I am barely pumping 60FPS let alone 90 (granted until further notice the Q2 is at 70hz for the time being until it's unlocked; same with hand tracking [not sure why yet but.. that is the case]) I'm generally not that aware of what it takes for a good VR experience, I .. rarely ... fly DCS in VR, like once every half year or so, so I'm definitely not the best in terms of what's recommended to improve your experience. That said doing a small amount of research it seems as though MSAA and the "filter" doesn't seem to improve performance; at least according to most people. Hence why I ended up just ending back up at 1.5PD and no AA because it made things the most legible for me personally. EDIT- ohhh did you buy a Gen 1 Quest, a black one? If that's the case you very likely will not be able to read the MFDs, I didn't catch the used part. The resolution on it is significantly lower than the new version; and being pentile OLED ... makes it even more difficult to read things.

I'm loving my Q2, and now trying to find the fine line of best visual quality / performance with my 1080Ti via Link (I've already had VirtualDesktop running and have been playing games like H3VR and Onward wireless the past week... absolutely LOVE being able to see things so clearly!) That said, I could not get VirtualDesktop to run DCS wirelessly; so I've had to end up on Link as that's the only way the Oculus software sees the HMD and will output DCS (because reasons... only had this issue with DCS thus far) I've had to reinstall Oculus Tray Tool and bump up my encoder resolution as for some reason it was incredibly low by default from my Quest1, and so far... it's been fine sailing. Encoder set and running at 3684, and running PD 1.5 in DCS. Pretty awesome to be able to actually read incredibly small text and finally see AND READ the text on MFDs.

Confirming this is indeed still an issue for me since 2.5.5 task manager also shows mine using little / no resources and even not responding sometimes for half a minute; sometimes if I pester it, it will go ahead and crash itself. Up until 2.5.5 I rarely even saw the splash screen. Still a bit annoying to see it sit and do nothing for half a minute.

This should answer anyone's questions about Mavs. Expect to wait.... even more.

So the next day I actually had zero issues. Something interesting to note: Besides being on Caucasus vs PG, the only real difference was range. At closer ranges they didn't want to lock up on targets at all. At range, it would lock them up lickety split.

Got in touch with Khopa for anyone else having this issue it came down to this: - Check the content of the file <dcs_installation_directory>/Scripts/MissionScripting.lua - Check if it match the file provided in <dcs_liberation_directory>/resources/scripts/MissionScripting.lua If it doesn't match replace the file in DCS scripts folder. In theory Liberation SHOULD be replacing that file when you launch it; it was not happening for me.

Came across this from Samurai 1-1's channel on Youtube by pure chance. Looked like fun. However this is all I ever get after flying. As far as I can say mission setup wise; doing a cold war 1965 on Caucasus Western Georgia [recommended], start date of Fall 1970 I've tried it twice now rebuilding the mission... twice; and this same error has popped up both times. edit- just tried modern timeline and same thing happened. Anyone have any ideas?

Still having issues where the IRs won't hit their targets or will aim for areas around targets but never actually hot-spots. I don't remember these things being so finicky and frustrating, but at closer ranges, they'll lock onto the grass areas alllllllllllllll around, but never the single bright white hotspot.... Surely this is wrong.

Personally I'm loving the additional feedback of the afterburner "fake" sound option. Small things like this allow us some feedback of what's going on, and detail sounds are very useful no matter how "unrealistic" they may be. I'd be okay with things going either way. It would be nice to have a global option to have "additional unrealistic noises" for things like the gear, air brakes, (do tail hooks whistle?), AB lighting, etc. edit - I just realized Bunny said the same thing. A slider, even as low as 3-way option would be nice.... and would be nice if it were truly global, including third-party addons. In XPlane11 there are mods that can add multiple sound effects and overlayed to your liking which is HUGE. In the racing sims, sounds are a make or break it situation on the edge of grip, DCS can be the same way at times. Telltale sounds no matter how unrealistic are a great option for those of us without feedback systems. But have it AS an option is great for those that DO have feedback systems. Thanks btd.

F16 raising and lowering landing gear no longer makes any noise; with or without helmet hearing.

Ran test again on all maps. Nevada and Persian Gulf seem to be fine. Caucasus and Normandy have the issue. Relocated in Caucasus to southeast corner of map to see if it was loading assets off map, but results are inconclusive to me. Tested again with A-10C, while it had a hiccup, not nearly the performance loss, but one ping to high CPU use, but never returned. Tried same test with AV8B using TPOD and DMT, issue remained. Maverick alone did not have poor results. I believe issue is related to DMT. System specs: i7 6700k @ 4.4Ghz 32GB DDR4 @ 4000Mhz Nvidia 1080Ti @ 3440x1440 DCS Open Beta v 2.5.6.45915 I don't have software to track FPS, but in Harrier it was nothing but stutters, it couldn't hold a constant FPS no matter how low or where it say, it was always stutters. av8b extreme CPU 3.trk A10C similar track av8b extreme CPU.trk

Not much to say, but I've tested this at least on Caucasus up to this point, and looking 090-365, I get incredible frame drops to single digits, and CPU churning to 100% until I fly basically direct north or north, northeast. Will test on other maps and return with findings. But it obviously makes it impossible to continue flying like this. Other test I have to make: does same occur using TPOD. av8b extreme CPU 2.trk