BrassEm

Much appreciation to Warlord64 for this and all his other work to make simming a much better place. I am delving back into the B-17 to see if there is still hope for this magnificent model. (Absolutely loved the Reflected campaigns for the BF-109 and FW-190 btw). Looks like the .json file sequence and content got changed. Just did a re-sequence of entries combining the new file and Warlords one and it seems to work. Not sure if its been covered elsewhere? Cheers, (Make sure you back-up the original .json file. ) EDIT: After more investigation it looks like the props may need to be fixed? If so I will update the json file link and note it. b-17g.lods.json

UPDATE: The option to remove the unwanted files was included in the 2.9.20.15010 update. Many thanks to Eagle Dynamics and BigNewy for the fix.

The Issue for the original post was that I need to remove residual files NOT removed by removing a commercial module through the DCS World dialogs.

Thanks guys for taking the time to write. I know it is only a few GB of data but even a few KB is too much if I don't need it. I am asking how to fully uninstall a module properly that wont break my DCS.

I've updated to 19.13478 and have not had the rig busters so far. I have only been testing on the George and the one Sinai map (not Iraq - my bad) for obvious reasons. Alignment doesn't appear to be the trigger.

G'day BigNewy, I have included some screenshots also. Launcher Screenshot 2025-08-16 070050.jpg shows that modules removed from the list and flagged in the "Available" button. Launcher a Screenshot 2025-08-16 070144.jpg shows the available modules for install. DCS start a Screenshot 2025-08-16 070533.jpg shows 4 modules flagged available for install by the red 4 over the modules button on the start screen. DCS start Screenshot 2025-08-16 070412.jpg shows modules that are available to install after DCS is started. Even though the files are still in their install directories, a selected module is redownloaded again. Also Is there any way to remove the install prompt for just those particular modules? I don't want it to effect other modules such as the soon to be released C130 for example. Thanks for your assistance with this issue. Correct removal of modules.zip

G'day, I was hoping to free up some SSD space by removing some modules. I went through the module manager installed tab option, and check marked the modules I wanted to remove entirely. Then clicked the "Delete selected". The modules no longer appear in module manager under the installed tab, but the files are still on the SSD. How do I get the files off my SSD to free up space without breaking DCS? Thanks UPDATE: The option to remove the unwanted files was included in the 2.9.20.15010 update. Many thanks to Eagle Dynamics and BigNewy for the fix.

@Bojanglez Extremely disappointing to hear this Bo! I was able to fly many shot/traps with the Hornet this morning on the George and didn't suffer the violent rig-breaking shakes. I am running 2.9.18.12722 MT and noticed there is update waiting when I start DCS. What version are you running? Also do you have the Iraq map by chance? Update; After a long session of motion tuning this morning it happened. The only thing out of the ordinary was the aircraft alignment prior to the episode. See pic. The whole aircraft was automatically shuffled across into alignment. And then once over the shuttle the shakes occurred. There has to be something with how this shuffle routine works that is causing a logic wigout!?

Easy as. Start with the basics like; do you know how to code missions for DCS world? ChatGPT said: Absolutely—I've worked with DCS World mission editing and scripting quite a bit. and go from there. Have fun! asked; give me a working .miz chatgtp said; Here is your working single-player mission file for DCS World on the Caucasus map: Download Simple_A10_Attack.miz Contents: Player Aircraft: A-10C II at Kutaisi (cold start, player controlled) Enemy Vehicles: BTR-80s placed nearby as ground targets No advanced scripting yet — just a basic setup to fly and attack NOTE: Ask "do you know about..." the thing you want to add to the mission to get detailed help. Ask for the FULL mission code as it will keep giving you code snippets. Start with the very basics and add one "feature" at a time to slowly build up the mission. (As with actual hand coding )

I don't think using MOD's is a valid way of testing for this fault. All tests should be done with vanilla ED files and NO MOD's installed at all. I do appreciate that you have taken the time to investigate and further highlight this major problem for carrier operations with motion, but It complicates the issue when MOD's become involved.

@Tea-Pig Sorry to hear your having issues there on the CVN-73. Thanks for posting the pics and files as it really helps. I haven't tried the A-4 yet. I will install it and try it out, but this will take a few days before I can get to that stage. (Once you get familiar with the F-18 I hope you will find that it is a very capable airframe.) NOTE: While looking at the readme documentation for the A4 MOD to install: #### Known Bugs and Incompatibilities - Pilot occasionally blacks out when throttling up to hook up to catapult on SuperCarrier. <<<<<<<<<<< Maybe high g load shaking perhaps @hannibal Things are really hectic now that I can start doing all the things I had planned for carrier ops, including at some stage, the "holy grail" of hooking into the stall effect for motion output. Great video (again!) that you posted the other day too!

Very nice setup there mate! Does your motion controller or motion interface software have a spike filter at all? If not then you would need to look at the telemetry from DCS and monitor/limit excess changes of rates there.

G'day Craig, Great work with adding motion to your rig. You won't look back if you've flown without motion (Ghosting) before. I've only just found out about SimHub and it ticks so many boxes. I too am transferring my rig to SimHub and looking at profiles for DCS. It would be good if there was a Forum for this where we can have a repository for DCS profiles and discussions. (I hate Discord.) At this time the only profile I have found is on the SimHub discord channel under "motion-profiles-sharing" for an F-18 (by ZeroCool). I have tested it with a replay and it seems to work okay. I have not flown it actual yet.

G'day Bojanglez, It would appear so. I have flown for several days with many cat shots without issue on the George Washington. I have not tried any other CVN yet. I am just really enjoying jumping in, getting to the cat and go without issues. It is not the answer as the CVN's are still broken, but at least we get to fly properly (and safely) on one.

G'day Hannibal, So many thanks to your findings, I have been catching up on much lost time. It is such a relief to hook up without fear of the rig breaking shakes. I have just been flying the Washington with all sorts of stupid alignments for the shot, and it all works good. I understand that the Forrestal will be different because that is a HeatBlur product, but I don't understand why 3 out of the 5 ED carriers are broken. From a programmers point of view they should all be accessing the same code? If the code is supposed to be the same for all, then it is a simple matter of comparing code and looking for the differences. I am sure it will be a matter of a wrong character typed in, or missing in the code, somewhere when integrating it into the last 3 carrier's. So I believe at this point in time for us motion rig users that use surge, the following carriers are broken and out of bounds until fixed. CVN-71 Theodore Roosevelt CVN-74 John C Stennis CVN-75 Harry S. Truman I have included a graph of a good working cat shot with surge and nose gear suspension deflection. The surge has been blunted with a 200hz notch filter in the export.lua in my futile attempt to remove the shakes. I can take it out now and get a crisper launch profile.

@hannibal I've sent you a PM.

It is getting up to 5 years since I have not been able to fly carrier ops because of this issue. Anyone with a full motion rig will have to address this problem that should not be there.

Great video! (And motion rigs!) Thanks for adding your voice to the issue. You mention about the oscillations around 15:27. The commanded oscillations are extreme and intermittent, and not part of any simulated event. You may be able to filter them to reduce the problem but at the expense of motion fidelity, negating the whole point.

I am very sorry to hear about the damage. I have the pause button on the throttle where my thumb usually sits so I can activate it in an instant. But that was after I was bitten as well. I have E-stops fitted as part of the primary build. I understand your concerns as a missile hit is sometimes impossible to predict. I am not aware of what motion controller you are using but I hope that there is some spike filter feature that you could investigate? It may be possible to put some sort of spike filter into the export.lua but that would need more research. Definitely need it for the ejection sequence for sure. Note that the filter does not work for the intermittent continuous 7.5g high frequency oscillation commanded by broken game code. (I have spike filters on my motion controllers.)

BrassEm

Same issue????

I bet you THIS reported problem has not fixed this update. Call it a hunch. It would appear that the shuttle tension algorithm may be borked. Just another hunch...

4 Years and another Major Supercarrier update and still not fixed. As previously described. --Accelerations: accel = LoGetAccelerationUnits() accel_longitudinal = accel.x <<<<<<<<<< local surge = accel.x Export.zip

All good motion controllers should have an emergency stop. It is a total emersion breaker to implement the stop at best. (And the 7.5g oscillation doesn't always happen every launch. And may, or may not, stop after starting.) Unfortunately the DCS program is calculating a wildly incorrect physical moment during the cat launch sequence due to a fault in program logic. We are at the mercy of Eagle Dynamics programmers for a fix.

I've disable outputting motion data for about 4 seconds at the start of a mission by adding some code to the export.lua file. (Extracted from my full export.lua) local t = LoGetModelTime() if t >= 4.0 then -- Allow 4 seconds for aircraft to settle on ground after loading in before outputting motion. -- output code here end