Adam

Is this on Open Beta, or also on Stable Release?

This appears to work with the current stable release, but Open Beta is still giving me the menu problem. (Which is only resolved by disabling Viacom in VA) Are there any known issues with VIACOM and the Open Beta?

Thank you! I've been having CTD's as well - normally at the start of a mission. I've just expected to crash the first time and get in the 2nd time around but I didn't think to regenerate shaders. I'll give it a try. Edit: By cleaning up shaders I'm assuming you mean deleting the FXO and MetaShaders2 directory in user\saved games\dcs\ ?

Maybe that's what it 'should' mean - but it looks like that's not always the case. :) I wasn't sure if I misunderstood, or whether there were other issues at play. Seems like I'm not the only one that's experienced IN RNG actually not quite being in range and falling short. For someone who's locked on and a SAM has launched, with 5 seconds counting down I've normally held out and dropped as soon as IN RNG shows up and then high-tail it out of there. Now I'm taking the approach that I need to calculate for IN RNG + 5 seconds or so before releasing when making my decision to stay on target or get out of dodge sooner and come back another day.

All we need is for either the Kiowa or Hind to be released now - and your choice would be made for you. ;) First in is probably going to get my purchase at the moment.

Could this be the magic bullet that is needed for VR (especially with DCS). 39% is a decent improvement. Couple that with new GPU's, and would that make 90FPS within the realms of possibility?

Thanks all! So I'm doing the right thing by waiting that extra 5 seconds - there are other variables at play and 'In Range' doesn't guarantee the range, it's just a calculated 'guess'. And great info about terminal programming. If that works - that will be very handy!

Hi, A few times now I have launched JDAM's as soon as the 'In Range' prompt shows up, just to have them fall short. I'm guessing that there's other variables at play (maybe wind?), that the targeting computer isn't initially taking into contact. I was just wondering what is the best way to counter this? At present I've been delaying my release by about 10 seconds, however I'm wondering if this is putting me at unnecessary risk when I have hostiles inbound being focused on the delay and was wondering if there's a more accurate way of knowing when JDAM's are truly in range? Thanks in advance.

Thank you!!

Thanks Maxsenna. I don't have a backup of my exports file. Does that mean I need to uninstall TacView, SRS, Voiceattack and Viacom, then install SRS, Voiceattack and Tacview - make a backup and then install Viacom so I have a fallback - or is there a more simpler method to get the settings to work with the other plugins again with a fresh exports?

Just wondering if anyone has VIACOM working OK with the Huey? I've got a strange problem where the radio and intercom menu's pop up and close randomly quite often (to the point that if I want to use them by the time I select what I want with the mouse it may close again). I've had to disable external plugins in voiceattack in order to get this to stop. The only external plugin I have in VA is Viacom. I also have SRS but that wasn't connected at the time. I did come across this post https://forums.eagle.ru/showthread.php?t=254572 which someone suggested Allow INCOCKPIT DCS CONTROLLED PTT so I have changed that - but it made no difference. Just wondering if there's a simple switch that might be causing this. Voiceattack has no logs of it being triggered, it just seems to be random.

Hi GunSlinger, Probably a real stupid question, but when you say 2D - are you saying you're running your Reverb with the same image in both lenses - so you're doubling your GPU performance at the sacrifice of a 2D image (but still have headmovement, etc) - or are you talking about just going back to monitors? If the former - can you advise how you switch the reverb to work in 2D only?

Hmm... good point. I saw the other thread here saying that VRAM makes a big difference with DCS. I wonder how long it will be for the 3080 'super' to come out. The 3090 is selling for almost $3kAUD (which rolls back to being around $2140 in USD. (A lot higher than the $1,499USD quoted on websites elsewhere), so that won't be an option. How long do you think we'll have to wait to see a larger VRAM 3080? I haven't followed nVidia in the past so aren't sure of what to expect.

Sorry - I haven't explained correctly. I absolutely agree - higher frametimes / lower FPS rates will definitely cause stuttering, but what I mean by the above is that thinking if I hit 45FPS I will get no stuttering because 45FPS should be fast enough for the eye is wrong. There are other factors that can cause stuttering, so by looking at the frame times / FPS as my center point for graphic settings I was doing myself a disservice. I need to get DCS operating smooth first, and then increase settings. If I hit my preferred frame times then fantastic - stop there - but I realise I need to be aware that I may need to stop before hitting my preferred frame times because other factors may cause stuttering before frametimes do - so focusing on FPS only was misleading me.

Any change of a gofundme page or something similar so that for those of us who appreciate the effort put into this can buy the original developers a beer or two?

Not even sure I can get away with one upgrade yet but wishful thinking. If I can just wondering which would serve me better? Upgrading my GPU from 2080 to 3080 or upgrading my Reverb from G1 to G2? (Solely looking at DCS experience here). Would prefer actual reasons why and thoughts, but for those without the time - I created a poll.

Thanks Hansangb, I think I'm right on the sweetspot. I close one eye, adjust the other until I get the sweetspot, and then do the other, and then go back to the first to make sure it's still there. I seem to have lucked out with my pupil distance being smack bang in the human average as well. :) There is a significant difference between 100% and 150% SS when it comes to readability. Again - maybe people just accept some blurriness and I have unrealistic expectations - I'm new to VR and are not sure what to accept but when I see the difference between 100 and 150 - it tells me it's not the lens, but it's the actual rendering of the graphics. If it was lens design I'd be expecting to see little to no improvement in clarity when upping SS as the lens would be 'off' focus. Hopefully there's a way that the cockpit can be altered to either be more resolution or skinned in a way to make it work better with VR without having to super sample in the near future. Everything else I can put up with - but I like my writing to be clear when reading it. Going back to the original topic, from what I can tell gleaning information here: a) I shouldn't be focusing on FPSVR to get smooth video. I should be lowering my settings until I get good/smooth ignoring FPSVR as it seems as though it's possible to get stuttering even when operating below 20m/s frame rates. (ie, stuttering isn't directly related to frame rates alone). b) FPSVR is more useful for checking for bottlenecks. ie poor graphics when GPU is fine but CPU is getting knocked about VRFPS will indicate that lowring graphics isn't going to do jack and I need to focus elsewhere. c) Use FPS as an assistant - but not as the primary tool. Focusing on FPS and frame rates alone will not guarantee no stuttering and I've been wasting my time chasing these with VRFPS.

I'm no expert - but I'll throw the following in... Try renaming your userfiles\saved games\dcs\config directory to config.old and let DCS recreate everything incase it's a mod/setting/etc. Make sure Windows Gaming DVR is disabled too. If the GPU is only at 35% and FPS's are so low - I'd agree.. .there's a setting somewhere that could be holding things back. What Settings do you have in WMR? Refresh rates, etc? Also what settings do you have in SteamVR (both globally, and for DCS specifically)?

Thanks Syndrome. I've already purchased the Huey. Having a great time in it, but I do get the feeling that sooner or later I'm going to want something I can push around a bit more. (I'm already blowing the main rotors off being a bit too aggressive over-banking as I come in hot and arrest the AS). But I have made the purchase now. I'm looking forward to the Gazelle but I'm not going to buy it until I've had a chance to actually demo it first. In the mean time ,the AH-6 mod will give me a bit more playtime. :)

I spoke too soon. I've turned that off and I'm still having problems in the Huey. The intercom and radio menu's randomly turn on and off very frequently. The only way I seem to be able to combat it is to turn off plugins in Voice Attack. (Or not have VA running at all). The only plugin I have for VA is Viacom so I'm assuming it's something playing up there, but I don't know what because I'm not giving it any commands. Any help would be greatly appreciated!

Oh sweet - that's a great way to test things out. Thank you! I have played with various mods and addons so it would be good to go back and compare to see what differences (if any) I'm running compared to a clean setup.

Aah -I think I get it. So you'll run as close as you can to the lower end of 45fps (or as close as you can get to 20ms) without going over so that you get the best graphics whilst still running at 45fps? Maybe that's how I should be trying to go about it. Change SS to 100%, setup everything else with what I'm willing to accept, and then just creep SS up until I get just below 20ms (or just above 45fps) and lock it in?

Yes please! I don't even own the A-10 and just reading this - I'm also convinced that it's very worthy to have as a disable option for those that do. :smilewink:

Cheers Taz. Yes - that make sense. If you're on the border/edge and a small % of increase will get you 'over the edge' for the next nicety then it's worth it. But otherwise if you're 'in the middle' to to speak - it's probably not. MSAA and SS seems to give a huge hit from what I can see. Does OC really allow you to enable it without a hit. (I thought O/C was smaller amounts - like at the very most up to 10% improvement)?

Hi, Total noob question I know. The reason I ask is as I understand it, Re-projection will lock my frames at 45fps unless I can get 90fps out of it, at which state then it will jump to 90fps. There is no 'in between'. If I'm capable at running 46fps, or at 89fps - the experience will be identical? If so - let's say my card without re-projection is running at around say 55fps without overclocking, and I can get 75fps if I overclock (I have no idea what sort of improvement I could even expect to get with overclocking and if this is even realistic), wouldn't re-projection still force it back to 45fps and my experience be identical between overclocking and not? I'd only be adding extra stress to the hardware for no return? If so, wouldn't that mean overclocking is only worth while if my FPS are getting close to 90FPS and overclocking will push me over the end, and in other situations I might as well not even bother? Or is there other factors at play here I'm unaware of? (I'm talking solely about GPU overclocking - ignoring CPU).