SkateZilla

Problem is, the A-10s are all Old, despite getting new wings, which were already made and sitting in a warehouse when FC shut down operations, the main fuselage still endures stress from the GAU/8. FC is gone, so is the tooling to build more, the only reason the A-10 is still in service, is because A. there is nothing close to doing that specific job on the same level. B. It would cost more to retire it than to operate it, C. Changes in congress at key times caused indecisions in the USAF Budget. So I can emphasize each point a little bit: A. It's obvious, there is no other platform with a GAU/8, they tried to mount one on a F-16, it didn't work out that well. The F-35A, being it's replacement, only because it's multi-role. But the Battlefield in the east, is not the type of battlefield where you can sit at 25K and lob LBGs and GPS Munitions all day, sometimes you gotta get down low and dirty, and I do not see the USAF sending a costly aircraft that has next to no AA Protection down low w/ only 180 rounds of GAU/22, it's like shooting NERK darts at a speeding car, not gonna do very much against armour. But the Airforce is consolidating, they don't want one aircraft specializing in one role, they want one aircraft that's OK at many, good at a few, to replace multiple, the Navy did the same thing, at one point it was the United States Department of Super Hornets, F-14s, A-7s, A-6s, S-3s, all gone off the deck, replaced by the F/A-18E/F/Gs. Shoot, if they could strap a trailer to the plane, it'd be replacing their COD as well. B. Retiring the A-10, Sending it to mothballs, training and re-assignment of personnel and delegating Airwing roles to another aircraft to train on, would cost more than simple keeping the A-10s in service in a reduced flight hour status. C. Every time the A-10 retirement is on the docket to be voted on, leadership and priorities change, and it gets dropped off the agenda. Make no mistake, the days are numbered, as each older airframe even w/ the new wings approaches the flight hour limits, they are being retired one after another, and w/ the fleet getting smaller, the remaining airframes are getting exponentially higher flight time, so their journey to their service life limit is hastened w/ every airframe they retire.

https://discord.gg/vZrJCA2euy

The A->C Shape is extremely different, Wing Root, Wings, Flaps, Flaperons, Leading Edge, Trailing Edge, Horizontal Stabs, Vertical Stabs, Part of the Lower Fuselage, Entire Landing Gear System, Aft Fuselage, Hook Compartment, Upper Fuselage/Nose Area, AAR System, etc. Although the A->C Avionics would be easy, the Flight Model would need to be a separate project. The B is a different animal altogether, as there are systems in the B's avionics not present in the A or C.

https://discord.gg/J7NRsnm6

This issue is related to the ModernMPD Mod.

no, pylon restrictions are hardcoded in the PFM/Systems DLL.

and the F-302.. Ooops.

Apologies, I have been working on a Mod Project, but at present it's at a slow pace as other things have taken priority, I was posting regular updates in my Wingtip Tanks Mod thread, As the mod originated from that, The New Mod when finished would be Titled: "F-5E Expansion", Previous Discussions: Mod Thread w/ other updates:

DCS Updater Utility v 03.29.2025 / 2.0.0.42 Change Log:

If we can re-produce this on the Legacy hornet, then it's a Legacy hornet bug, with the avionics and not changes to the super hornet.

I would need to see a screenshot of the command prompt box.

I am looking into the changes to the pages, but I am busy this month travelling for work, plus most of my CJS Codepath has already transistioned to v2.5 and integrating the new cockpit. For anyone with the crashes, it maybe the ModernMPD Files, as they also cause issues w/ the SA Page, Please attach your DCS.log files so I can start some tracebacks.

Literally the first post of this thread.

DCS_updater.exe update 2.9.13.6818.2@release This worked for me, make sure you're running from Command Prompt, not PowerShell. And Make sure it's being run from the <root><path.to>\DCS World\Bin\ Folder

the only things missing are the new campaigns, I am working at remote locations so I have not had time to add them to the chart.

Apologies, you must also choose a preset in the preset panel, It's *supposed* to auto to default depending on the parameters, but I suspect that subroutine isnt firing off correctly. Selected Preset will have a missile Icon on it.

It says no data because no build is actually selected here.

ModernMPD v2.1.43 was integrated into the latest CJS Super Hornet Mod (2.4.1 and 2.4.2), since it's separated from the legacy file structure wise now. I didn't really check for features not working, I simply integrated the files from the \Super Hornet\ folders into the CJS Cockpit scripts folders and textures etc. I know the MPDs are different colors, the HUD has correct dashed and solid lines, etc. didnt check for "Color" SA. But since we are now Separated from the "Merge" installing, the CJS Super Hornet resides independently in the \Saved Games\ Folder, and does not overwrite or modify any Legacy hornet files, instead we are now using our own cockpit Scripts on top of the legacy hornet's. But the folder name is \Cockpit\Scripts\ just like the legacy, instead of \Cockpit1 <or 2>\Scripts, like it was w/ the merge install setup prior to v2.4

there's 2 profile folders, one in Saved Games, one in DCS Root. App Scans both. But the setting itself is populated based off what's set in the options.lua under ["graphics"], then ["multiMonitorSetup"]

The monitor Profiles are in \Config\MonitorSetup\

Graphics profiles? I never put a delete option, but \Saved Games\DCS\Config\Presets, Should be a Backup, Default, Preset 01->05, PresetVR. Just delete the folders, and re-launch the app and it should re-populate.

Please note, there still maybe "Drag/Drop" Exception Errors. These are caused by a sub function of a sub thread, trying to invoke changes on the UI thread incorrectly or without permission. I've scanned through most of the functions and fixed a bunch, but there definitely still may be some hiding. I'd ask if you get one, as soon as it comes up, click continue, and then right click the Apps log dialog, choose open, copy contents and paste here, or save into a new txt and attach, so I can get a rough idea of what function is running when it trips.

DCS Updater Utility v 03.02.2025 / 2.0.0.41 Change Log:

If they don't have the F/A-18C installed, then the module will not load due to the Modules Required / Rules: In the entry.lua, they can change true to false, which will load the module, but they will still not be able to fly the aircraft as the DLLs and dependent code is not installed nor activated by DRM for them. --[[ DEFINE F/A-18C REQ. ]] ["F/A-18C"] = {required = true}, -- [[ DEV NOTE: DEDICATED SERVER, OR PLAYERS W/O DCS:FA-18C THAT WANT TO SEE AI / OTHER PLAYERS NEED TO SET TO FALSE ]] For the Record though, it DOES Say DCS: F/A-18C is Required in the Install Notes, Credits, etc.

Sorry guys/gals/fans, There's a slight delay, as the testers found some issues that needed to be fixed. For the most part everything was functioning as intended, But I had to make revisions to the new version parsing system as I did not include provisions for Hotfixes or Assembly.PrivatePart version fields. That fix plus a few other changes are now being testing, and I might have to adjust a few other things. Hopefully Next weekend, or if I can get remote access from the Hotelli, mid-week.