Sandman1330

Another data point. After I launched, something went very wrong on the boat behind me.... And on attempt 2, I narrowly managed to dodge being hit by olive on taxi, only to have the wonderfully professional deck crew give her a launch go ahead at exactly the same time as me. With predictable results. Attempt 3, Tomcats crashed and exploded on CAT 3/4. I guess I'll have to skip to past the AAR, which sucks because I wanted to do the whole experience... I get these are DCS bugs. But ED better sort out these problems, or guys like BD will stop making campaigns, and/or guys like me will stop paying for them... I've been trying to play through this campaign for 6 months now, but keep getting stalled by bugs... RODF M14.trk

Ahhhhh I recognize those guys! Love it!

I wonder if someone could help me. There is an RCAF skin built into DCS, but the pilot models that come with it are generic (no patches or anything). I'd like to edit those to add Canadian patches, but the Huey seems to have a different file layout for liveries. Anyone know where the file is that I can edit to edit this specific livery's pilot models? Nevermind - found it! C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Bazar\Liveries\uh-1h\Canadian Force

Forgive me if this is obvious, but did you set rock as A/A waypoint in the HSI data page? You can then see where your radar or SA page cursor is and get yourself heading in the right direction until you find him on your own radar.

Huh, strange! I played that mission yesterday and all went well, except the inability to complete after landing. I don’t envy campaign creators these days, chasing new bugs every update!

Did the SA3 not engage Sluggo on his run-in? He called defending, and the 3 popped up on my TOO page, so I engaged and destroyed it with HARM. I brought one HARM back. My problem is, the mission won't acknowledge as complete. I refueled, followed him to the boat, and landed with DCS Marshal comms as directed. However, no mission completion, score 50...

I'm just replaying, and I think I know why I waited forever for Red to engage. It's happened again on my second run through - Red has run off at the high port, waaaaay to the east. Like, single handedly invading Syria far, over 40 miles. When called to engage, he then needs to truck waaaaay back west to actually engage!

Chalk up another one. No reduction in FPS, still very playable, but minimal increase and also showing CPU bound in the F18 Syria free flight mission.

Is this DCS bug supposed to be fixed now? I'm starting the campaign from scratch (had to take a break halfway through earlier), and still I'm getting no datalink on missions 4 and 5.

I’ve used process lasso in the past, but not recently. Maybe I’ll give it another try.

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