Twwhitey

I apparently have $17 in Bonus Points that expire on 06/01/2020. How can I leverage those to purchase the P-51D in my shopping cart? It's not readily apparent how to apply those funds to my checkout?

Ahhh interesting - ok that’s kinda what I expected but good to know so I figured I’d ask anyhow. I’m not sure how the AirbaseID issue manifests itself in game but as always kudos to you for all of your hard work on this... your efforts to maintain and improve are greatly appreciated!

Hey Surrexen- question for you. I’m about to start a fresh v121 single player run on Clear Field with persistence on... My question is given the impressiveness & complexity of the A2A defense scripting is - is there an actual tangible advantage to knocking out the EW sites on the map? I.e. will there be a subsequent impact to enemy caps, or other air defenses, etc? Or are they just basically other targets? I was going to focus early efforts on the SA-10s & SA-11s to open things a bit but I was wondering if knocking the EW sites out might take some of the heat off as well. Just curious thanks!

Yep I can confirm this as well. With Voiceattack running it won't load and will hang at 10% on the loading screen. Running a repair will resolve the problem... until you try to run with Voiceattack again.

Ditto this. Without going the Warthog stick “extension” route swapping out for this spring made ALL the difference in the world especially when it comes to AAR. I’m immensely more proficient than I ever thought was possible... the stock spring is way too firm for precise maneuvering especially when you turn on wake turbulence and need to incorporate a sustained hold in a particular direction. Highly recommend it was worth every penny if you are considering it...

I for one will definitely be getting the super carrier and would’ve thought a lot of F-14 & F/A-18 owners will as well. Who knows tho That said I would hope as mentioned above it won’t be too considerably hard to swap out the Stennis for the new carrier in the mission editor on the players end if we wanted to... I’m wondering if swapping out the Stennis for the SuperCarrier will be as simple as selecting it via a drop down like u can for planes in the ME... If anything it would be great to know if you foresee any issues doing so with regards to your scripting? Is there any Stennis specific scripting going on?

VRSS settings are detailed about midway down the page here: https://www.nvidia.com/en-us/geforce/news/nvidia-geforce-ces-2020-game-ready-driver/ You should see a setting called Virtual Reality - Variable Rate Super Sampling which you’d want to set to “Adaptive” I suppose at some point I’ll try the new drivers but quite frankly I don’t want to mess with my system at the moment as it’s running well and I don’t want to break anything

Not to add any more fuel to the debate (I do agree with dburne though that the vast majority of nVidia settings don’t appear to have any effect in DCS VR whatsoever) but this update to the GeForce drivers sounds intriguing. “Alongside the frame rate limit, this driver also includes Variable Rate Super Sampling (VRSS). This improves image quality in VR games by separating shading rate and resolution to improve different parts of the frame that you’re focused on in VR.” Looks like the driver hasn’t been released yet but is imminent. I’ve been using a months old driver under the adage ‘if it ain’t broke don’t fix it’ but I’d be interested to try this to reduce some of the weird aliasing/shimmering I still get around carriers etc.

But this is only the case for the current active session though right? i.e. damage inflicted to airfields is not persistent so next time you fire up the mission you’d need to re-bomb the airfields again right?

In my experience (as a solo player who wants to focus on A2G missions) that the enemy caps will eventually overwhelm you in time even when you enable the friendly carrier, airfields caps and bring fighter support to your area of activity. I think the question was asked before and I dont think the airfields are destroyable nor persistent so I don’t think that’s a means of reducing enemy AirPower. In my case I actually went in and edited the “airdefenses.lua” mission file (in the .miz mission file) to disable 4 of the 6 enemy airfield caps and increased the respawn rate of the 2 remaining cap airfields to like 30 minutes. It’s definitely helped... depending on which airfields caps you disable you can semi-tailor what air threats you’ll deal with but if you have a long transit to your target in say the A-10C you’ll be sweating some enemy threats and running for home eventually. The problem with these edits is you need to make them every time the mission is updated sooooooo Would be GREAT :smilewink: if Surrexen could add user adjustable triggers/flags enabling/disabling the various enemy caps to dial up/down the volume of threats without the need to edit the files directly in a future iteration. Just a thought! :thumbup:

For the record I seem to recall getting error indications in the export log/window as well but that didn’t entirely seem to doom the export and subsequent import. The export did indeed run (and produce an export file) which I then imported (which also produced some error indications scattered in the results messaging). Long story short it *appeared* to have the desired results as I have not had to re-train WSR and Voiceattack/VCP seem to work just as well as before on a completely fresh install. It’s worth a little tinkering in my book vs going through the whole training ordeal again but probably not worth hours of effort if it’s stubborn....

Yeah it's quite an old tool but apparently Windows Speech Recognition hasn't changed much since 2004. The download from MSFT should unpack a simple .exe (SpProfileMgr.exe) which should run in Windows 10. It does on my system (Windows 10 Pro v1903 see screenshot).

I believe this is what you are looking for. The Microsoft Speech Recognition Profile Manager tool allows you to export and import windows speech recognition training profiles. It’s not the greatest tool (I got some error messages when I re-imported my profile) but I *think* it worked in a recent wholesale reinstall of Windows 10 on my gaming system. https://www.microsoft.com/en-us/download/details.aspx?id=22358

Man that’s so weird. I did a repair and reset the Openbeta saved games folder too. Oh well, I’ll keep playing around with it. Thanks for confirming!!

Interesting ok thanks for trying. I’ll try PP mode the. I’m going to re-download your mission.. perhaps something is corrupted.

F/A-18... it appears to only crash with 2000lbs bombs the GBU-31s (both variants using TOO node), and GBU-16...

Hey Surrexen - I'm having an issue in this mission. The game crashes to desktop when I pickle either the GBU-31, GBU-31V(3)/B or the GBU-16. I've tested a couple other missions and I can pickle those bombs no problem so it appears it's happening in just this mission. I was thinking it might be related to the custom scripting around the custom pickle sounds so I removed the Snowfox Deathwatch.lua script load trigger in the Mission Editor and tested again and it still crashes. Surrexen - are there any other scripts or events you are tapping into that would occur the instant you "pickle" those weapons. I can get it to crash to desktop 100% with those bombs. Question - is anyone else out there seeing this crash or issue with just those specific bombs? I've repaired DCS and even reset my DCS.OpenBeta saved games folder and no dice. Interested to know if you have any ideas or if I'm the only one experiencing an issue with those bombs?

No crash folder in the Game Logs folder as I can tell. I did your recommended reset of the Saved Games/DCS.OpenBeta folder and it still crashes just when using the bombs mentioned. I will say it appears the crash is specific to the mission I posted in the first post. (I loaded up a practice mission I created in NTTR and I can drop those bombs no problem). Note the mission designer was using a script that plays custom sounds using the On.Shot event... I was thinking it might be something related to that scripting so I removed the script altogether and it still crashes. I'm going to reach out to the mission designer and ask if there might be any other events that he's tapping into when the pickle button would be pressed.

BTW - that uploaded track is NOT from the mission that crashes so disregard that track file.... I just re-ran the mission (using GBU-31s) got the crash to desktop and there was no Last Mission Track file in the Temp folder you mentioned so it appears that we're out of luck.

Thanks Bignewy. I'll try the crash advice (really didn't want to mess with my system too much as it's working great otherwise but I'll try). Quick follow up. Tried GBU-38's same exact setup, same exact mission and I was able to pickle off four, one after another no issue. Then attempted to pickle off a GBU-12 (or whatever the middle sized one is... not a -16) and at the cue when pickled it CTD'd. (See attached last mission track file). Note, in case it matters, I'm trying to bomb several surface naval vessels at sea (not buildings, etc)... Now that I know about the last mission track file I'll go back to the original GBU-31 attempt and get a track of that crash too LastMissionTrack.trk

Noticed i was (1) minor update version behind in the OB... did an update (to 2.5.5.39384)... no change, still crashes as before. Log file of that attempt attached... Note I don't get any DCS.exe Crash message, error code or anything, just drops to desktop when I press the Pickle button.:glare: I will say I had a CTD the other day using a GBU-16 (i.e. another 2000lbs bomb I believe) as well (right upon pickle like this) however I've never noticed any issues with anything smaller bombs. Rockets, guns, missles, smaller bombs, rockeyes, other CBU's never seen a crash like this. Anyhow this one is certainly reproducible in my book. dcs_GBU_Crash_log_25539384.zip

I've experienced pretty frequent crashes to desktop using the big GBU-31s (both variants) in the F/A-18 so I decided to give reproduction a try to see if I could get it work somehow... nope. Same mission, same target, (4) attempts in a row, (2) using the GBU-31(V)3/B and (2) GBU-31. I'm using a TGP to designate a target in TOO mode. Warm up TGP and GBU's after takeoff Set GBU's to TOO Mode Set EFUZE to INST After both are warm Point track the target Designate it using TDC (confirm coords are xferred to GBU) Wait a few miles inside IN RNG Pickle single GBU and crashes to desktop. After the 3rd crash tried a repair, no improvement... it crashed again. Log file and mission files attached, not sure if there are any other files you need if so, let me know. GBU31_crash_mission_files.zip GPU31_crash_log_file.zip

So I'm using the OTT tray tool exclusively to set/change the ASW mode for DCS (I use the OTT Profiles capability where I set ASW to OFF or Auto, SS to 1.4). I tried dabbling a bit with the keystrokes you've mentioned above but they didn't appear to work within DCS at first glance so I've been exiting out, changing the profile and restarting DCS (ensuring I get the audio queue that my profile is enabled). I'll re-try those... do they 100% work in real-time from WITHIN DCS? I'll also drop the PD/SS to 1.3 to see if I notice any difference. I did pull up the OTT overlay briefly the other day to check the frametime perf and noticed I believe I was getting 10ms-12ms frametimes yet still enabling ASW Auto automatically triggered ASW on just about all the time - which again is weird. At the end of the day, the fresh Win10 Pro install coupled with the dedicated effort to really clean & tweak the OS using some guides I found online (disabling unnecessary services, limiting installed & start-up apps, removing unnecessary bloatware, etc.) did appear to bear some benefits. (And this is on Win10 build 1903 which is supposedly one of the worst builds for gaming). My "test" mission is the F/A-18 Caucasus Instant Action "Free Flight" mission... when entering that mission I just descend & fly low level circles over the town you start above looking around, etc. and I was previously unable to activate any MSAA (x2) AND SS >1.0 at the same time without getting juddering/ghosting (I could enable one or the other but not both)... now with the new install and settings mentioned zero juddering/ghosting, I can fly right above buildings and it's a smooth 80fps. I was literally shocked when I disabled ASW and it was smooth (I had spent hours and hours over the previous months tweaking my previous install, nVidia settings, DCS settings, driver updates, etc. to no solution). I only mention this for those on the fence who may have purchased a pre-installed system... it's a real pain-in-the-a## starting from scratch (took several days of effort) but appears to be worth the hassle.

Hey dburne - while on the subject of ASW and the "Auto" setting... you seem very knowledgeable on the subject and on the Rift S in general. Got a question for you. Are you aware of any setting or configuration option where you are able to modify the threshold at which ASW kicks in? Let me explain... I had a pre-configured system that shipped with Win10 Home which was working pretty well however I made the decision to perform a "fresh, completely clean" Window 10 Pro install (as I was annoyed with a lot of pre-installed bloatware that came with the system and the fact that Win10 auto updates are hard to impede in Win10 home... plus the OCD in me just wanted to know I had a 100% fresh install). Anyhow when firing up DCS for the first time with the Rift (ASW in Auto) after installing and tweaking for a few days I noticed that same mission on the same hardware, identical nvidia & DCS settings runs 100% of the time @ 40fps (in comparison on the previous Win10Home install it would run largely at 80fps but dropped at times of lots of activity to 40fps). This led me to believe the new Win10Pro install was running WORSE until on a whim I set ASW to OFF only to realize the game runs like 98% of the time at 80fps... no juddering, no ghosting... even with MSAA 2x/pd 1.4 (which I could never get to work w/o juddering)... a solid 80fps almost all the time (except for maybe when there's lots of explosions, or maybe a bit of judder when flying over tons of trees at really low level or coming off a low level bomb run it'll hiccup for a bit). Switching ASW to Auto and it immediately goes to 40fps... even when out in the middle of nowhere over the ocean. leads me to believe something weird is going on with my setup. Optimally I'd like to have ASW set to auto for the 2% of the time I need it to smooth things out but it seems for whatever reason once it's set to auto it just turns on all the time even when I don't really need it. I had not experienced this before... Curious if you have any thoughts? Any settings around that you are aware of?

What you are seeing is the effect of Valves Motion Smoothing algorithm (at least with regards to #1&2 above). Oculus ASW has a similar, but IMO, less dramatic effect as it’s a more refined algorithm at this point. I found the Valves Motion Smoothing to be pretty bad at times especially in the Viper cockpit, lots of warping of cockpit elements during high speed maneuvering (even during takeoff)which is a real bummer given the overall quality of the Index vs the Rift You’ll see those effects go away if you switch off motion smoothing but then you may need to deal with a juddery / choppy experience... it’s all about trade offs