Sandman1330

I’m finding very minimal improvement after MT. I suspect the stronger CPU meant I was closer to GPU bottlenecking even before MT. Now I’m hard GPU bottlenecked. It DOES seem to help a fair bit more in busy missions though, where even the X3D struggled.

How do I do this? Would like to try it. Interestingly, using the new MT exe file, I only get the triangle screen once now. Still goes twice in the ST exe file.

The other aspect not yet discussed here (but it has been identified in other threads) is suppression. I've had scenarios where I've unloaded an entire rocket salvo or burst of 30mm at an armoured vehicle, and while in the midst of receiving that salvo, taken fire from the vehicle's pintle mounted MG. Even if that vehicle doesn't take a direct rocket hit (it's conceivable it could survive hits only in proximity), it shouldn't be shooting back. No-one is exposing themselves outside the turret to man the pintle MG, and the coax / main weapons would have their sights shredded or at least masked by the smoke and dust. But I do believe suppression is another area identified for fix already...

Thanks, my experience sounds very similar to yours, even down to the sound. It's been doing this since I got my Reverb G2 (3 years now?). In that time I've done multiple DCS reinstalls (for various reasons), and even a complete system wipe and re-install (new hard drive). I suspect the only thing that may solve it is more direct WMR integration with DCS. MSFS 2020 is a very very smooth transition between VR and flat panel, that would be the gold standard we'll hopefully one day get to.

Thanks guys. It's not a centering issue (I have tried re-centering, in the hope it was just off-center and stuck in the VR hangar wall or something). It's very strange. For diagnosis purposes, do you guys get the "triangle transition" from WMR to DCS more than once? I always get it twice. It shows, then kicks back to the cliffhouse, then shows again and goes into DCS. With controllers turned on, it does this 3 times - and ends up black screen. It's almost like it sticks in some feedback loop and "misses" the chance to catch DCS as it loads, leaving me stuck outside DCS (as you'd see happen if you kicked yourself back to the cliffhouse in game, no way to get back into DCS even though DCS still thinks you're in VR).

Thx for the reply. Nope, no mods. Necksafer would make me sick, lol.

Reverb G2 using WMR (OpenXR). When I start up DCS, I get the "triangle transition" from WMR to DCS typically twice. Sometimes it does it three times. If it does it three times, it seems to miss the "window" to catch DCS, and DCS will start on the monitor in VR mode, but all I get is black screen in the headset. It seems to do the triangle screen three times if my controllers are turned on, and twice if they aren't. Anyone else have the same issues?

The truth? Because most people enjoy this module for what is is - a very accurate (but not perfect) representation of an iconic military helicopter. To put things into perspective, the multi million dollar Level D simulator I train on yearly doesn't fly anything like the real thing. The DCS Huey already flies (and looks) better than a multi million dollar advanced training simulator. It isn't perfect, but it's pretty darn good. I'd let them focus on the real issues that need resolving, and (hopefully one day!) a refresh Huey 2.0, or maybe even a Twin. Something like a 1 degree difference in the external model for the horizontal stabs does not impact the enjoyment of the module for 99.9% of players. I admire your dedication, but for most this isn't an issue worth worrying about.

Are you seriously worried about such a small discrepancy? You shouldn’t even be looking at it below 40kts. I’d rather the dev team focus on the bigger issues personally. And 1500hrs flying helicopters has taught me even the real ones don’t adhere to the book numbers that closely.

This is accurate. The airspeed indicator is actually inaccurate below 40kts in the real aircraft (and most others). Below 40kts you shouldn't be looking at your instruments for landing cues, you need to be looking outside.

Great news! I think for many (myself included) it would be perfectly acceptable for saves to not be compatible with newer updates. For the purposes of long campaign missions it wouldn’t be too much of a factor. Bravo for keeping this alive.

Thanks! But I've long since for real upgraded to a Virpil base. Only just recently moved away from the X56 throttle to a Virpil as well, the throttle held me for quite some time.

Look at the configs used for that data. CL used the configs from the DCS Dogfighters server https://discord.gg/dogfighters. In those given configs, and with G modelling on, the Viper has close to the worst STR of all 4th Gen. The Hornet and M2K rule the roost in those configs. With full fuel / external tanks etc, things even out a bit. PS - if you join our discord you’ll find updated charts that reflect the M2K’s latest FM update, it is still top tier STR but is now beat by the STR king, F18.

I was able to chase this one down, and started a new bug report as it's not related to George:

Referencing this post here: I was able to replicate the bug. It does not have anything to do with George. How to replicate: 1. Set up a simple mission with 2 apaches and several ground targets. 2. Start in one apache, fire a few, have your wingman fire a few. 3. Switch to your wingman's apache using Combined Arms 4. Fire a few more. 5. After a few shots, you will end up with hellfires showing on the wpn page that are not on your racks. You'll see them depicted on WPN but they are not on the rack. As a result, you can't fire any more hellfires, even though the system thinks you are still firing them (the symbology on the TADS will show msl fire, TOF countdown, everything. But nothing is launched, and those ghost missiles stay depicted on the WPN page). Attached is a short track file that replicates the bug. Apache hellfire bug.trk

Either way it wasn’t the back scatter . Thanks for your input though.

I wonder if I should start a new thread, as I don’t think this is related to George at all… I’m not sure if the OP tried firing them himself or not, so it could be what is causing his issues or could be unrelated.

Yes I tried other targets, and it shouldn’t matter to the actual launching of the hellfire. Yes it would affect accuracy but the hellfire would still leave the rail. Both external view and the wpn page showed the missiles were present on the rails. I did take some damage but it was after the problem started (when I couldn’t hellfire I went in for guns). It’s also happened twice in two back to back missions now. Edit: oh I understand your question now, whether that specific missile was there or not, I’m not sure TBH. If that is the issue it’s clearly a bug, trying to fire a missile that isn’t present.

I think there is something to this, but I don't think it's just George. It always happens late (an hour or more) into a liberation mission, so short track files are hard to come by. But what happens is hellfires simply won't fire at all. George won't fire them, I've tried from the pilot seat to have him de-WAS and just lase, then I WAS hellfire but nothing comes off the rail when I attempt to fire them. Then I switched to the CPG seat, and still, nothing comes off the rail. I pull the trigger and nothing happens. I just noticed as I'm drafting this, I DO get the missile countdown on the TADS from the CPG seat. Again, super hard to replicate as it only happens late in a liberation mission. And I've also switched from the apache I started in to my wingman's aircraft using combined arms, not sure if that is a causal factor either. I'll share my track here anyway, but be aware it's a long one... I'd love to share a short one but I haven't been able to replicate it in a short mission yet. Track file: https://1drv.ms/u/s!Ascm8Kmu7NR0hIA5Jfhx0kpoX9uFlQ?e=dWFlyu And here's an attempt at making a video of the problem. I apologize as I'm not a content creator and I am not well versed in creating video, especially in VR. As I have the problem evident right now I want to get something out soonest.

Thx BD. That is the tactic I do currently use, but it still proves quite tedious. I understand your viewpoint on it, even if it’s not the answer I wanted to hear

If you have textures (not terrain textures) to high, try bumping them down to medium. I found my issue was high textures in the Apache and other newer / high detailed modules were maxing out my VRAM, even with 16GB, and overflowing into my system RAM (also 32GB). Both were maxing out!

G'Day BD, I'm re-engaging on R1DF now that the Tomcat bugs have been sorted out. While I was on "break", I played Sedlo's excellent (free) campaign, Bold Cheetah. He has a feature built in that allows the player to "jump to the action," so to speak. I would like to request maybe you consider something similar. I have been very slow to purchase campaigns, and the main reason is DCS lacks the ability to save game. I don't have tons of time to play, so when I can spare 2hrs to play a campaign mission, I do love flying the mission from start to finish (and always do, at least the first time around). However, this being DCS, things happen. The game crashes (as we all know from recent memory!), and we get killed / mess up. I've now managed to get killed twice on Mission 9, once when the SA3 spawned directly underneath me and shot me down without much chance to evade, and a second time when one of the AAA managed a golden BB shot that took me out on a strafe (I mean, it was REALLY a golden BB. First burst shot right to the pilot. Who trains the gunnery of the optically sighted ground AI? We should hire them). I am really, really trying to find the patience to go through everything, again, a third time to finish the mission. I mean, you're 2 hours in when you get shot down, the game crashes, whatever. Then you have to do those 2 hours again (and maybe again and again) to progress in the mission. If we could have a "skip ahead" option that skips the administrative stuff - air start over the objective area kind of deal, that would make it much easier to get back on the horse. I'll be honest, this kind of thing has really reduced the number of campaigns that I buy. It's just not enjoyable when you have to dedicate so much time again and again, going through the same script, same voiceovers, again and again. Until DCS allows us to save games (which they have no plan to do I'm told), this would go a long way towards making the campaigns more approachable. Thanks for listening! And of course, have a great holiday! Edit: A second, smaller suggestion: When we are given grids for targets (as you get a lot of in M9), can we also get the elevation? It doesn't auto-populate, so the pod doesn't go to the right area, and one has to go into F10 map to find the elevation.

Strange. My first time through it stalled out when red was supposed to engage, just didn’t progress from there. Tried a second time and all worked properly. I think sometimes a trigger or flag just doesn’t fire, leaving the mission “stalled.”

Does this affect the hellfire though? I thought it was just for the range finder.

Try dropping textures down a notch (not terrain textures, just textures). I had a similar slideshow in MP and this fixed it. I believe the high textures of not just the Apache, but Hind and other player flown aircraft overwhelmed first my VRAM, then system RAM. Both were maxed out. Dropping textures to medium brought the memory load down and the stutters disappeared. I was surprised as I have 16GB VRAM and 32GB system RAM!