Nightstorm

As many of you know, I'm a big fan of the F22 and ever since it's re-release on 2/20 I've been tweaking and adjusting things for my own use. I have no intention of releasing a second version however, I could release a mod for the mod. I was considering two versions. One that would be 100% compatible with the stock release of the F22 mod for multi-player and another with additional changes for single player use. Both would REQUIRE the new version of the base MOD on the first page of this thread. As some may know many of the files in the new version are encrypted, and as such can't be modified that much. However, most of the cockpit scripts are not encrypted. I first set out to make small improvements and bug fixes but then expanded to try and make the non-functional pages do something. As I communicated to the dev team, I mean no disrespect to them in any way. What they've released FOR FREE is in a word AWESOME. There's nothing wrong with trying to build upon that work in my opinion. After all, isn't that how innovation works? Someone builds a better mouse trap by improving on the original. Here are some screen shots of the cockpit displays I'm working on:

I've hit supersonic a few times w/o afterburners. I would imagine there are multiple factors that affect it. Altitude/air density, aircraft weight etc.

I just came across this myself. One advantage I clearly see over Joy2Key is the number of buttons recognized. I can now use RS Mapper to program all of the switches on the Wingwing F/A18 start up panel for example. Echoing what Meathawk asked is there any command line option to force RS Mapper to select a specific profile / or RSMapper File on start up? Understanding that you can have multiple profiles under on RSMAPPER file, I'm guessing you would have to have a way to tell it what RSMAPPER file to load beyond "use last file" option under preferences. If that were so, you could have an RSMAPPER file with one profile each for different aircraft and be able to load them with a script or batch file. In any case, this is an AWESOME software utility that gives us more options and flexibility. Thank you for your efforts and sharing this with the community!

NICE, before I even had a chance to test the others Thank you!

Thanks, I just PM'd you as well

OUTSTANDING WORK! I spent most of yesterday working on similar things for the same reasons After I click "start" I don't want to touch a mouse again until I'm ready to click "stop". So here's an issue I'm having and maybe we can resolve it together. I have controls sync turned on as I'm sure you do. However my throttles are always the opposite of where I have them. If Off they are on IDLE, if IDLE they're on OFF. I don't know why. There is, as far as I've been able to tell only the one command for each Throttle "L/R_cutoff" which appears to be a toggle. Now I spearated the controls with this code but the starting position is still wrong. I'd love to be able to define a separate OFF and IDLE for each engine. -- {down = L_cutoff, up = L_cutoff, name = _('Throttle (Left) - OFF/IDLE'), category = _('F-22A HOTAS')}, --ORIGINAL LINE -- {down = R_cutoff, up = R_cutoff, name = _('Throttle (Right) - OFF/IDLE'), category = _('F-22A HOTAS')}, --ORIGINAL LINE {down = L_cutoff, value_down = 0.0, name = _('Throttle (Left) - OFF'), category = _('F-22A HOTAS')}, --ADDED {down = R_cutoff, value_down = 0.0, name = _('Throttle (Right) - OFF'), category = _('F-22A HOTAS')}, --ADDED {down = L_cutoff, value_down = 1.0, name = _('Throttle (Left) - IDLE'), category = _('F-22A HOTAS')}, --ADDED {down = R_cutoff, value_down = 1.0, name = _('Throttle (Right) - IDLE'), category = _('F-22A HOTAS')}, --ADDED Oh, and the APU. I'd be great to have an OFF command for it. I've been trying to get that to work as well. I had trouble cold starting the jet at first b/c I bound APU to the APU switch on the WingWing throttle panel and it wouldn't allow it to go to "Start" and then back to "Arm". If you look at the switch in the 22 pit and use a mouse on it's its actually Off/ARM/RUN with RUN being a momentary position. At least I think it was labeled "RUN" you get the idea though. I'd like to have APU Start and APU OFF so that you can bind them to a momentary switch. That way you could toggle it one way to start the APU and the other to stop it w/o having to click the OFF position in the cockpit. I tried various value_down/up statements without success last night. {down = APU, up = APU, name = _('APU Start'), category = _('F-22A HOTAS')}, Thanks, now off to test your code with the lights!

It has been stated that it will work on both the current open beta and stable.

The release website was also posted right above. It has all of the information.

That wasn't a post by the dev, it was a post by me. And that refers to the old version. Which is why I pulled that link down and made a note in bold with a date stamp at the bottom of the first post. There was also the same post above.

With the impending release of the new improved and awesome sounding F-22 Mod coming out tomorrow at noon Eastern. I'm pulling this download offline as it will be deprecated and could cause some confusion.

You should be able to get that working using this path under your SAVED GAMES folder. "C:\Users\XXX\Saved Games\DCS\Sounds\Speech\ENG\Common" Note that its not Sounds\Speech\Sound\ENG\Common. The Sound folder was dropped some time ago.

Yep that was it :) Thanks, works great now.

Great, ok I will try that! Thanks!

Sure. I have two, one for normal and one for VR. options_NORM.lua options_VR.lua

Unfortunately no change with 9.3. SHF F7 has no menu.

I will also test 9.3 and see what I see. Thanks!

Well, I've tried everything I can think of. Versions 9.1 and 9.2 just won't work on my system. The previous version still does. 8.1? I've confirmed with Hunting =2 that it's loading. In fact with 9.2 I'm now getting an error message in red text at the upper left of the loading screen referencing a value $HUDSharpenFactor = 0.8 in the user_var_initialization.ini saying it's unrecognized. I'm not sure what the problem is. I'll just stick to the previous version. It allows me to increase the saturation, brightness and sharpness in VR. The version that works for me has ShaderFixes that are dated from 1/9/21 so that was v8.1. I've confirmed global cockpit illumination is off and I've tested water low or high and both 2D and 3D. I can't get the menu to load on the newer versions. It would also appear that 8.2 works for me. That was the version with shaders dated 1/29/21.

I will test this today to see how it goes. I know that I have cockpit illumination off but I'm pretty sure water is set to high.

While it stinks that this bug appears to be present, at least I know it wasn't just me and my install. All of the sudden my AIM-120C's won't track anything in TWS or in RWS with a lock. They just go stupid. In another thread it's been pointed out that the issue may be related to their anti-counter measures not working. That would explain why in a short test I took off and shot down my AWACS and a civilian jet with no trouble. They didn't employ CM. I used to be able to track multiple targets in TWS mode and ripple fire AMRAAMs at them with a high degree of success. Now they don't seem to work at all.

8.1 was working fine as was the version before it. However trying 9.1 I can no longer get the SHF-F7 display to come up. I even removed all other mods and shaders with no effect. Cleared the shader chache as well. Any ideas?

Updated 2/5/21 to v1.8 / v1.8.1 https://www.digitalcombatsimulator.com/en/files/3314044/ Includes new 600 gallon tanks.

If I'm looking at this right, with MSAAX2, no mod Avg: 65.500 (7 FPS hit), and with No MSAA, Mod with color + cockpit sharpen + FXAA Avg: 64.900 (8 FPS hit). And then if you turn it all on: MSAA2X, Mod with color + cockpit sharpen + FXAA Avg: 58.000 (15 FPS hit). That's the sum of the other two options by themselves. MSAAX2 gives you a 7 FPS hit and the mod with all on gives an additional 8 FPS hit for a total of 15 FPS. That's worth it to me.

Yea.....wow. What ^ said.

Updated 1/27/21 for DCS 2.5.6.60645 Open Beta. New options added. The first link will take you to the updated file in user files.