cptmrcalm

I heard that too.. but thats not the case. Thats why I mentioned my last about rearming with 4 and going back out. I suspect a bug with dropping the 2 HARMS and keeping the other two.

I was chasing an F18. Had 4 Harms, 1 HTS pod, 4 AIM120s and 1 Tank. To catch him, I decided to drop 2 Harm's (in board stations) and the single tank. Fired all of my AIM120s and turned away. No hung stations. No damage. No issues. Selected the HARMs to tackle a HAWK site a little later. As always, I have the HARMS in POS mode. Using the HTS pod, I select the HAWK and get a good return. 2 from 3. Time to fire. Nothing. Huh? select it again. Nothing. Check in air to ground mode, check systems. Nothing. Select again, and switch the other screen to the WPN screen to make sure the HARM is indeed on. It is. Interestingly, the HARM changed itself to the default mode when you first power it on. (with the cross hairs). Changed it back to POS mode. Fire. Nothing. Make sure target is locked and repeat. Nothing. HARM back to default state. Any ideas? Landed thereafter. Rearmed with same loadout and took off and was able to fire all 4 HARMS at the HAWK site no issues. POS mode using the HTS pod. (confirming the stations were fine even though I had no warning lights) Very weird. Could only be a bug.

How are you getting on? Are you still having problems? Always good to check on progress and see where we are. Helps others who may well give up. I was having these problems myself (with my slightly older rig, 9900k, 3200mhz 32gb ddr4 and 3090) recently after 2 years of happy flying. Turned out to be an automatcially downloaded update for WMR For Steam VR. Had to go lkg_release on the 1.60 beta to fix it. All has been well since. But curious to see if your issues are something else and if you solve them before I go buying any new upgrades.

One thing to bear in mind is that you might be experiencing issues with the drivers. Apologies, I sped read the topic so I might have missed it. But if you are using WMR for Steam VR (Note: not WMR that you can access via the settings menu within Windows - but the actual "WMR for Steam VR" that you install within steam) then there have been at times versions of it that have upset a few gamers here and there. Recently, they released two updates. One dated 6th Oct (1.3.58) and then one shortly after (1.3.60 <- in BETA state only). Both of these version messed up DCS. Micro stutters -ghosting and general poor performance. For me, it crashed my system after 5 - 10 minutes. After many hours of wasted re-installs and messing around with settings - it turned out that it was these updates that caused the issues. For me, the latest version (1.3.60) was a BETA version that I realised I had to opt into within steam to actually see it as available. Once I did that and installed it I found it still didnt help. Some time later I found out that I could select: "lkg_release - lkg_release" as an option within the WMR for steam vr 1.3.60 settings. Performance for me now is certainly exceptable and playable as it had been before these two updates. I run a 9900k (overclocked on all cores to 5ghz) 32 GB of ddr4 ram at 3200mhz. 3090 stock. HP Reverb G2 set at 100% optics with reporjection off. I could list the DCS settings here, but its a case of tweaking to you find the balance that you like. apply them - test - tweak things off and on until you find the fluid motion you like. But as I say, its certainly fluid enough for me. You always want more, but if I am honest - its certainly good enough for me to never return to a flat screen again.

Hi there. Yes, its steam DCS I use. For VR you have to run both WMR and Steam VR which then calls upon the WMR for steam vr. Hopefully, all will be well now. The only issue is getting word to the WMR for steam VR team that the latest version is buggy.

hi there. just to report back to you Lester my good man... (and for anyone else reading this) - it seems that running the Windows Mixed Reality for SteamVR in the latest "lkg_release - lkg_release" seems to have fixed it having now just done a very quick flight in single player with a test mission that failed repeatedly. I am flying tonight on the buddyspike server tonight in PVP so I will see how it goes. But so far - 30 minute test is looking good. I could tell it was going to work within the first 30 seconds. It fails again, I will report back later.

Blast! Although I think its the Windows Mixed Reality for Steam VR driver. Need to look in to how to roll back the version. I havent fully read this properly - but a quick scan has caused me to send the link for myself to look into later. Also - just seen this. posted 15 hours ago.

Hi all. Wondered if anyone here has experienced anything like what I am about to describe. (my guess is no) I have a Reverb G2. Been using it for around two years now. Very happy with it. When I fly DCS – I only ever join the blueflag servers for PVP. I don’t fly single player very much at all. Friday 7th October I was doing my usual flying on the server and all was great. Saturday 8th October my world changed. I suddenly get constant crashes with DCS on the server. Here’s the kicker. I have not touched anything. Haven’t installed anything. Haven’t changed any settings. The symptoms are repeatable and happen every time. The sim is a little choppy and stutter when I enter the world. (very subtle and intermittent). I take off and within 5 minutes the VR headset goes black and SteamVR crashes. With the options of restart or close SteamVR. The sim is still running and I can see it on the desktop- no matter which I do (close SteamVR or restart it) It runs very slowly – around 10fps. If I happen to able to see the hud (as the headset at this point is dead) I can land the plane albeit a challenge at those frame rates. I am not seeking graphic settings advice here because I have been using the same settings for around 2 years happily. But why has it suddenly decided to do this? I gave the dates above in the hope that someone might advise that an automatic update may have took place on the 8th October with either Windows Mixed Reality, Windows, SteamVR, DCS or Windows Mixed Reality for SteamVR). What I have tried: I’ve changed USB ports for the headset in case it was a USB thing. No difference. I’ve done the obvious things AFTER the 8th October to see if it helped but it didn’t. (updated nvidia drivers, windows updates) I cleared environment data with the headset and at first I thought it had fixed it – but it didn’t. I’ve re-installed DCS, SteamVR, Windows Mixed Reality and the Windows Mixed Realty for SteamVR as well. All no good. Luckily, I have a valve index too. That, I can say, runs fine. If I was a betting man -I would say it was the Windows Mixed Reality for SteamVR. But I can’t roll back to a previous install. That did have an update around that time. It was available that week – but I don’t allow automatic updates, however, It could have been that? Anyone any advice? if i get some feedback - i can start looking into the suggestions and go as far as to provide log files and provide settings details and versions numbers etc. Just looking at some guidance at this point for what to look out for. PS. the headset (G2) runs fine with other titles, such as REC Room, Skyrim VR etc. This happens only with DCS. (hence why I have posted here)

Thanks guys. I guess its down to personal budget. I haven't heard any complaints about the module itself - so I am aware its meant to be good. I do like the F14. One of my favourites since childhood. Like I say, I'll keep it on the wish list until it comes down to something more affordable.

Hi all. Difficult to put into words my thoughts on the pricing of these modules. Being a steam user of DCS, I wonder has the F14 module been on a more reasonable sale price with ED? Steam at the moment only has ever shown 15%, which makes the price fall down from insanely high to now eye watering. I am not sure what it is I am trying to achieve here by casting my thoughts. But £65 for a flight module I think is so high a price to make it feel offensive. I bought the F16 and F18 at £30 each (with a year or so apart) and thought that price to be a little steep at the time. I feel now that those modules were worth it. At that price. I am not sure I would have bought the two as quickly as I did if they had been £65 -probably only buying one. Is the F14 so much more a module over the F16 and F18? I am not talking about performance of the jet, but I guess the 3d model and systems and sound etc etc. I just find it hard to believe that I would be getting that much more. I've no doubt its a great module btw. I don't mean to suggest its poor in any way. Everyone has the right to charge what they feel its worth and I understand the model of business here adopted by ED and its partners. I suppose I can just keep it on my wish-list for it to fall down to more reasonable but expensive £30+ .

Hi there. I was online on a PVP server. Took off in an f16. Took down 2 players - first one no real hard manoeuvres - second one a short hi g turn and lots of speed to get away. Nothing too out of the ordinary and nothing prolonged for any length of time. Perhaps a 90 degree hard turn and then a high speed 30 degree dive - got to around 1.5 Mach. No biggy. Nothing too strenuous. On my way out - i was left with just a single aim120 on the right wing. Fuel was low but plenty to get home. Around 3000lbs i reckon. I was at around 30,000 feet. Had been burning for around 60 seconds and calmed to level flight. Throttled back to around 95% mil power and was just feeling chuffed that I had battled it out and won. Was flying nicely for around 1 minute or so and suddenly the aircraft slowly began to rise. Ok. push forward slightly.. ever so slowly and it began to dip. Odd. Then rise... and then dip. Had not taken a hit - not even a debris scratch. Odd. Then it turned with a full rudder to the right. I saw it coming and managed to dip the nose to stop it stalling and flat spinning. But despite the speed and height it would NOT stop spinning. Now. I noticed when I looked back that the flaperons were at maximum! (like the ramp start procedure and you extend them to full to test) Had the server got some sort of random failures per chance? Never been a big fan of random failures as these will always happen more than they would in reality. But each to their own. Just never seen that before. I've had the f16 bounce up and down at certain speeds and dives. Again, another odd thing - but i can settle that with some height and throttle control. Now I am sure its all explainable, but it would be nice to know. Like i say, no chance of being hit by anything. No heat seekers and nothing going off next to me. Quite a clean kill from me. Just very odd. (ps. for what its worth - I was having problems with the keyboard. I went to type: "good fight bro" and i couldnt press the "G" key. Also, the D key was activating some sort of windows prompt. I rebooted the pc and the keyboard was fine. Any chance i had accidently hit something during the game which caused the F16 to behave strangely?)

Its a palit 3090 and I think it's OC from stock. I haven't OC the card myself in any way. I can crank some of the settings up within game and it still be an acceptable framerate. so those settings I can move around still. I may still turn things up here and there as I progress. I didnt get as much time this weekend as I might have liked. Trouble is, its hard to pin it down because it could be a combination of settings that cause it. But for now at least - its a relief to be free from it.

Here are the settings I have found that I can push to without blue screen flickering. Now it could be I could push things further but have decided that its good enough. I am enjoying the extra performance with MSAA off. I learned too that SSLR is bad frame hit too. (which i really wanted to keep because its subtle - but looks gorgeous) I know this isn't about performance -its about stopping the blue flickering. But I think the too go hand in hand. I may never know what causes it - hopefully drivers and DCS software improvements might fix it in future. Again, slow fps is one thing -flickering is something that I felt was too much to live with. i think the lesson here is - if you are experiencing the flickering, then default to the VR profile and change each feature step by step until the flickering comes back,- then simply go back one stage. At least I know its not the headset itself. Thank for the reply guys and I hope this helps someone.

Hi all. An update. It is definitely DCS and not the headset. I looked at your settings Speed-Of-Heat. (once again, nice job) The Nvidia settings didn't seem to make any difference. I changed what I had to match your settings. There were a few things I hadn't got the same as you ie. no setting for "monitor technology" and no setting for "preferred refresh rate dell". But those aren't important. I also made the same settings in WMR (which I had never seen before- took me a while to find that page within steam vr). In addition, I also saw that we had the same Steam VR settings too. But bang - the jarring blue flashes. My process of illumination got a little lost when I started turning things down to medium from high and playing around with MSAA etc - in a step by step fashion.. (It started to get a little funky - and I started to get some weird effects with the water. I could at certain angles see what looked like a tropical ocean (cyan blues and what looked like corral reefs all this within the Persian gulf map btw.) Then a crash. (to be honest - I did that many jump in and outs that I am not surprised) I then decided to set the VR profile to default. The one that DCS provides which knocks everything down and turns things off. But guess what - it worked! No blue flashes at all. So then I decided to knock things up bit by bit. Things I wanted. The one that definitely caused the blue flashes to return again was the visibility distance. Ultra is a no no as was high setting. But the high setting might have been paired up with MSAA at the time. I am still playing around and will confirm it when I have more time. I've just spent about 3 hours straight on it. But once I have done some more testing (longer flights) and are happy I will post what settings I have. There's definitely something not right here because you expect to fall in frame rates when you crank stuff up- sure. But not get flashes. For example, if you fly at x12 or so ( using Control Z ) you can see the VR struggling. You get the black spaces around you where the VR cant keep up. But here, you don't get the blue flashes. Bear in mind. MSF2020 which (no offence to DCS here) makes DCS look so out dated and basic by comparison. The detail that sim presents is breathe taking and yet - no flashes. Sigh. Almost there. (need to sleep now) I really hope this ends up helping someone.

Thanks for that dburne . My version is Steam though and also the beta version too. I do recall changing something a while ago, back when I had the index. Tatting about as I do with no fear of consequences. Whatever it was I changed I suddenly became aware of the issue. I think what i need to do is check out speed-of-heat's guide and see if it happens after doing that. Performance is fair to good and I have no doubt I can improve things. I will of course report back if I end up fixing it -but I have a feeling that by doing the guide above -and it does disappear - I wont know what it was that caused it. Just one of those I wish someone would just say.. "yeah..its X - you just need to do Y to remove it" If I do a "verify installation" with steam - will it save my plane controller settings? If I end up doing a compete re-install: If I am in "F16 Sim settings" and "export profile" - does it save only the" f16 sim controller settings"? or all controller settings for all aircraft? Always wondered this. (Yes I know I know - RTFM.)

Hi there. Super quick as I pass by... Tracking could be... room has to be bright doesn't it so i might try that. Usually somewhat dim. i have tried the USB thing. Saw that knocking about elsewhere. But can confirm a change of USB port does nothing. (although only tried USB 3.0 so far) And again, remember... all is well in other titles. Weird one this.

Hi all. I have seen a very nice thread which I am going to take a look at as soon as I can. My 3090 Settings for my G2 - Virtual Reality - ED Forums (eagle.ru) This guy - wow. Thank you. I am hoping to go through it step by step. I have seen some recommendations from others, but sadly, none of them can seem to fix my issue. The issue I am having is with DCS only. MSFS2020 is fine, as is half life alyx. Now I will check that again to make sure. I only get to hop onto the PC every so often, so it takes me ages to really nail something down. But it happened again in DCS last night so I went right ahead and fired up MSFS2020 right afterwards to quickly see if it happened and it didn't. Every so often, I will get these blue flashes. It happened in a quick mission I made in an F18 and happened last night in an F16 in a heavy multiplayer session. I was ok for the first 10 minutes, then I looked around the cockpit and FLASH!! its quite jarring. Now, as I type, I have suddenly remembered something. On my Index I would have the occasional same thing - only the screen would go black for a moment. talking like 10th of second - a very quick flash. Now I reckon its setting I need to look for. Something that needs to be off or cranked up. Has anyone had this? I've got HP on stand by. They want me to install a piece of software so they can collect as much data from me to look into it. At first, it sounded like a hardware issue - but because other titles seem to be ok, it sounds like a software issue. I really am hoping it's one of those "smack forehead" moments and I simply need to change an nvidia setting or something within DCS. I have a 3090, a i9900k, 32GB ram and I am running off M.2's. Latest windows as of Monday -same for Nvidia.

Just like to chime in here and help out. I've been having this problem for weeks. Trouble is - I only get the odd moment here and there to test and try out which is why it has taken me ages to solve. Long story short - but there is a setting for WMR found within "windows settings". (and oddly, not also within the VR space which threw me) Go to "Mixed Reality" and look for "Headset Display" - (3rd one down) and scroll down until you come across "Input Switching". Set that to Manual. I use Voice Attack for things like: "Centre" (snaps head to middle of cockpit) and "Mouse" (the Win+Y key) etc... There is a tiny sensor within the G2 I didn't even know about. What was happening with me is that I would lift the headset slightly to see a light switch or move a glass out of the way and I would place the headset back down over my face (talking only a inch or so) and lose the mouse. Drove me nuts!! The G2 would say to WMR "he's took his headset off - switch mouse to desktop please" -(even though i hadn't) Sometimes Win+Y would work to get the mouse back-sometimes it wouldn't. So its the automatic feature that's rubbish. It sounds good in theory - but doesn't always work. Now what they need to do is fix the dam turning VR off when you leave it idle for too long. Instead of simply turning the screens off as a safety feature, they turn the whole VR eco system off - meaning that DCS will assume you have killed off the VR and close! Tusk! how very Microsoft! (although I will say that MSFS2020 has a VERY nice way of implementing VR. You simply press Shift+Tab (i think it is) to turn VR on and off seamlessly. Very impressive. So if your VR closes - you can simply get it back by pressing those keys, or assign it to Voice Attack like I do) DCS - if your listening, (I doubt it) THAT would be very nice indeed!) I have an new interesting issue I am hoping to solve - I am probably going to have to post it as I dare say I will find an answer.

just a little bump

Hi there. Love the model. Excellent work. Tried this multiplayer. The back seater (the instructor slot) cant hear engine sound. Also the canopy doesnt close when the pilot closes it. Strangely, for the back seater -it does close on take off despite it already being closed for the pilot. Is this something likely to be fixed?

@Svend_Dellepude. your message appeared after I sent mine as I must have not refreshed the page. Doesn't seem to matter for me. I can leave the air brake on for a good while and still have the issue. Of course, I say "issue" but I suppose I mean "behaviour". It is what it is.

Finally had a chance to test. Yes. Indeed the new functions are: You can go from fully forward to full aft on the switch (HOTAS a10 warthog) in one motion, passing the centre position and erect fully (snigger snigger) the air brake. Fine. As before. However, clicking fully forward again is ignored. You can no longer do this. So you have to click into the centre position first. Wait. And then click forward again to close the air brake fully. Separate to all of this - and to those reading with any interest (probably very few!), when you click fully back to open the brake, you can pause its travel state by clicking into this centre position to freeze the position of the air brake - so long as you catch it at the desired extent. (in case you dont want it fully upright). Not news to many regular fliers - but to any new-comers, this may be of use. Im ok with the new function. It just caught me off guard is all. But interesting that the function has indeed changed.

The plot thickens... Interesting. Maaaaaan times like this I wish i could fly more often. Desperate to try this out now. I was getting worried it was just my age. Memory is getting terrible and self doubt is common place these days!!! lol One thing is for sure:- It wasnt like this before.

Hi guys. I don't know if the switch was animated before and to be honest, its not something I've noticed even now. I haven't touched anything else. I don't use target since I use the default assigned to me by DCS. All I know is that before, I could flick from air brake up to air brake off in one fluid motion and you got what you expected. Now you cant. I'll admit that I am curious to know why. But not so much that I must lose sleep over it. Like I say, now that I know its changed, I can discipline myself to hold it in neutral before pushing on the switch to lower the air brake. In fact. I was about to post this and ended up staring out of the window for a moment. I don't get to fly very often, so I cant test now. But now I think about it, I think I can pull back on the air brake switch in one full motion - but cant reverse that. Meaning I can raise the air brake by rapidly clicking back the switch aft - but the issue is with closing. I have to click half way - wait - then one more click forward to close. So now I think about it - I think its just the closing of the air brake that has changed. Windows updates is all I've done - maybe that's messed with the button inputs or something. I don't know. But guys, seriously -its interesting for sure. But not desperate.

Indeed. I thought to raise it because as I say, this wasn't the case before the latest update. Before that, all was well. I suspect the change was something to do with enabling something else to function. Or perhaps, it was a side effect to something completely unrelated. It was really only to help a developer if it was an accident. It may have been intentional which is fine. As i say, now that I know how it behaves, I can work around it. But it caught me off guard and got me killed twice since the behaviour had changed from before. I ended up a sitting duck, and my foe salivated before taking the killing shot - not believing his luck as I just fell down to earth like a floating leaf! lol