Scope666

Check out my post here: https://forums.eagle.ru/showpost.php?p=2961114&postcount=170 At the very least it might give you some ideas, or you can download the package and try it out.

I have it, I do think it's a lot more comfortable. Its also crazy easy to adjust since you're just turning a knob. If you liked the way the Rift felt, you'll probably like this better. (had a Rift briefly and returned it)

I finished OPF and have been going through the NTTR Red Flag 16-2... it's nice but doesn't hold a candle to Ranger79's work. When I'm finished with R.F. I'm going back and running all of OPF AGAIN, it's that great. :)

Just wanted to say thanks for the guide. It's SO much better not having the detents in there! :)

Saw something like this when I tried to purchase within DCS. Went to the store via browser and solved the problem.

Yep, got it twice today on Missions 3 and 4. Just completed Mission 3 without incident so it seems like it's not affecting progress.

I can confirm this behavior. Somebody destroys the 1st target before you get a chance to. I watched in pride as my GBU hit the already destroyed targets in F6 view. Also it feels like the 2nd target's coordinates are off. I dropped a few weapons and they always seemed to miss but land in the same spot. This is the ZSU with a bunch of soldiers right on a mountain peak. This was with DCS 1.5.5.59744 Update 1

I've completed missions 1-7 so far by rolling back to 1.5.4 ... the only negative is you can't have labels on since it apparently also rolls back the version of OPF which still had it enforced. It makes it tougher but also more rewarding so I can't complain. Having a blast so far ... awesome work Ranger79!

Scope's X52 Pro profile for the A10C Hello, I've been tweaking this for a long time, and I thought it was time to share. I also thought it would be good to get it out there for feedback and possible improvement ideas, as there's still lots of shift mappings that can be added. The concept of this was to try and match the real HOTAS setup of the A10C as depicted in the manual. I especially tried to honor what is on the throttle vs what's on the stick as much as possible considering the fewer hats we have to work with. Here's the layout: Attached is the .pr0 for the Saitek software as well as the .lua.diff file to import into DCS. I've mapped as much as possible directly in DCS, and the only thing special that the .pr0 does is create bands for the axis controls, as it works more reliably this way. When zoom is on an analog axis for example, the image will shake sometimes because the controls drift. Also the speedbrake is setup so that it DOESN'T repeat, so you can slide it back and forth a few times to get the desired amount of braking. The reason for this if you leave the axis full back or full forward, and you have a key set to repeat, it will block other key commands. The way I have it the repeat will automatically stop. You'll want to go into your modifiers and add joystick button 6 like so: Also make sure Enable Clutch Mode is NOT checked: DCS_A-10C_X52_Pro.zip

Hello, I've been tweaking this for a long time, and I thought it was time to share. I also thought it would be good to get it out there for feedback and possible improvement ideas, as there's still lots of shift mappings that can be added. The concept of this was to try and match the real HOTAS setup of the A10C as depicted in the manual. I especially tried to honor what is on the throttle vs what's on the stick as much as possible considering the fewer hats we have to work with. Here's the layout: Attached is the .pr0 for the Saitek software as well as the .lua.diff file to import into DCS. I've mapped as much as possible directly in DCS, and the only thing special that the .pr0 does is create bands for the axis controls, as it works more reliably this way. When zoom is on an analog axis for example, the image will shake sometimes because the controls drift. Also the speedbrake is setup so that it DOESN'T repeat, so you can slide it back and forth a few times to get the desired amount of braking. You'll want to go into your modifiers and add joystick button 6 like so: Also make sure Enable Clutch Mode is NOT checked: DCS_A-10C_X52_Pro.zip

Not that I know of, but you can use your Steam CD key(s) on the standalone version, which does allow rollback, that's what I did.

Me too ... 1.5.4 let's the Chinooks land. :)

Thanks for that. I was just wondering if this was an issue introduced in 1.5.5, and if a temp rollback to 1.5.4 can be used as a workaround while we wait for ED to fix the helo bug.

I'm curious if the Chinooks would be able to land in 1.5.4, as they get stuck and never land in 1.5.5 (Mission 2 and some others I believe)

This happened to me too, exactly the same way on a few of my attempts. My successful run was with the stand-alone version. Some previous failed attempts were on Steam.

For me in mission 1 the wing wouldn't start their engines if I asked for startup permission 1st. The one time I had my engines fully running before asking was the time the wing started their engines. Very strange ED bugs I believe.

This also happened to me, just something to be aware of in mission 1.

In case anyone else runs into this bug, here's the video I shot of the startup sequence. Should be done processing in a few minutes: (actually made it to the end once I finally got them to start their engines)

Ok, that's REALLY weird. I didn't talk to them at all and this time they started their engines. I actually shot a video of it in case it proves to be useful. Thanks for your help, your work on this is nothing short of AMAZING!

Ok, no dice with the standalone version with a fresh uninstall / reinstall of the campaign, and the MissionEditor folder renamed. I'm doing just the APU to power the radio, requesting startup, they acknowledge ok to startup, and then the wing never starts their engines. They're just sitting there with their wing lights blinking.

Yes, I did that last night, but I'll try it again now. I have the Steam and stand alone versions, so can work with either for testing. Also both are on 1.5.5

I have tried EVERYTHING and they still won't start their engines. From everything I've read they're supposed to start their engines when you request engine startup. (Kutaisi is giving me permission to startup)

I renamed MissionEditor to MissionEditorBAK, and no change. The flight simply won't start their engines. I also requested startup from ATC before anything else, and I'm using HOTAS Mic Fwd to talk to them.

Exact same problem here. Tried the uninstall / reinstall as well. I'm on the Steam version if that matters.