SkateZilla

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.

Pretty sure ED is moving to Blender, lol.. But they only make plugins for Max Versions they have licenses for.

in my experience, the 2:1 Pulldown in resolution trend was discontinued in 2004ish. Shoot in my studio renders for TV Shows and Movies the Normal, Metallic and Roughness Maps are 2x the size of the general albedo maps... As for Formats, it's BC7 For Transparency and BC1 without.

I have a new version in internal testing w/ the testers, so barring any major issues... end of the week... TM.

Right Click Build Slot, Set Sim Path, on the Sub Menu, Choose "Manually Set Sim Path", then set to the \DCS\ Root folder.

For Those that arent "Graphically Knowledge-able" The Current FCS: MiG-29's Normal Maps are: 2048x2048 for 4,194,304 px a 400% / 4x Increase to a Surface ^2 Texture is: 4096x4096 for 16,777,216 px, 4K ^2 Textures are standard for pretty much everything now. Put the Pitchforks away.

Trust me, I'm aware of the limitations of not being able to use modelviewer for liveries. I've prolly made more liveries than I can count, and unofficial templates for a while, I think in the last 5 years, I've launched modelviewer more than DCS itself.

Of Models being Stolen, or Models being dumped from memory? I'm not comfortable treading into this topic, as it borderlines piracy etc etc, That being said, the subject chain of discussion on the matter should prolly stop now.

w/ EDCE in place, it would be a scrambled mess. I was referring to current .EDM models.

the .EDM Format did not protect against models being converted, I'll leave it at that, ED's Models were being exported and re-used in other games/sims by individuals. in fact, even now, with the right tools, I can dump anything from VRAM Memory and import it into 3DS.

ModelViewer Currently does not have the DRM interface.

I am not employed ED, That being said, for a block I Super Hornet most of the data is available upon request, block II not so much, Here's the caveat, for a normal civilian. ED has had in the past some form of agreements with Boeing, so limits applied to a normal person requesting data for a sim might not apply. Another Caveat is the F-35 is exported to ~10 Countries already with another 6 investing in the program. While the Super Hornet is a 2 Country Pony.

Hence: "And Beyond"

The LOD0 of each shape was unlocked, the Core files / Luas were not. *Edit Apparently the LUAs were unlocked as well*

I have requested the multiple threads be merged w/ this one, Also, there is a patch coming, the holidays kind of put a stop to work for a few weeks but, I do have a changelog / bug tracker pinned in the CJS Discord: v2.4.241129 Bug Tracker: Fixed Internally: Fixed GBU-32 not being recognized on STA2. Fixed GBU-31 V2 and V4 Not being recognized. Fixed STA-2 Split Store Bombs Mounting to wrong pylon. Fixed Mis-link in CLSID Swap on STA2 MB Offset for Mk-82, Corrected STA-2 offset 2X GBU-32 w/ CLSID SWAP. Fixed UFCD on Legacy hornet black out, Removed Old Cpt04 Textures. Changed CJS Cockpit Livery Name from "default" to "CJS SUPER HORNETS". Revisions to Ordinance table. Cleaned unused stores, adjusted formatting. Adjustments to AIM-120/AIM-9 Split Stores. Adjusted ADU773 Weight and LAU-115C Drag Qtys. Added Strobe Ident. Pattern Drop down to Aircraft Properties for Player. Strobe Seq. can be set for player unit in mission editor. External Lighting system revised to get aircraft property from mission editor and set pattern. Added Check Boxes for all SUU-79 and SUU-80 Pylons in Mission Editor. Adding New restrictions lists for the pylons removal checkboxes. Flight model, Adjusted Center Of Mass and Inertia slightly. Fixed, NVG / Helmet Attachment Device Init. does not detect Helmet Device from Mission Editor. Fixed Aircraft Fall off deck when parked on edge. PFM Collision Model and AI Pos. for Rear Gear Adjusted slightly. Suspension Dynamics Adjusted Slightly. Collision Model Revisions. Removed Small / Extra Details from Collision Model. Re-configured mesh names and settings to match legacy damage model. Animated Wing Fold, Control Surfaces. Integrated Invisible Rack system for bombs and offsets. New Invisible Rack is setup to mount stores to Connectors instead of X,Y,Z, Coordinates. Due to some stores being older EDMs, mounting points for single stores or X,Y,Z Coordinates would shift per model. Adjusted Elements Order for Better Firing Seq. of stores and weight distribution. In Progress: Network Arguments for Growler Pods. Not CJS Responsibility: - C-130 Anubis Mod, Invalid Number/String WsType in File, Code Fix for C-130 was pinned in Discord Channel. - Similar issue w/ other mods and weapon WsTypes - AIM-120D/AIM-174 and Other Hot Swap Missile Mods that replace AIM-120B/AIM-9 variants.

Wouldn't hold my breathe, they are not part of the variant modelled, and well outside the scope of the variant modelled, plus since they are cosmetic, if they include them, the systems would have to be written or adjusted.

Well I've been busy for a long time, so we're even. I'm currently re-writing the version parsing, which will then be integrated into build and module scanning, as well as merging some module scan functions into a single function, which will resolve any version# issues for good, as well as making it less work when adding new modules, since everything would be further unified and condensed into a single function vs multiple. Everything else that's broken (ie MT Modes etc), have already been fixed internally. I have a Loooooooooooooooooooooooong change log, but I cannot release the next public build until after I finish the scan re-writes, and a few features that have already been integrated make it to the public DCS Builds.

It's because it's assuming / seeing 2.9.10 is 2.9.1, even if I parse the version string into major, minor, sub-versioning values. It'll be fixed when I get time to work on it add a 2.9.10 parameter like I've done for older versions that get to above x.x.9 and get another build out, lots of under the hood changes, so, it wont be after holidays as I'm still working 5x15 hr days, in remote locations.