SkateZilla

definately on my whiteboard list, as my mouse has developed an unwanted random double click symptom.

- Uninstall Button Launches DCS_Updater, accidental clicks I can see being a bit destructive, I could add a Prompt stop w/ toggle to enable/disable it. - Access to your account and auto installs will not happen, as I would need to integrate into ED's user infrastructure and authorization systems, and I am 100% sure they would not be sending me that information, I don't think there's ANY external application that signs into ED's servers. First Post troubleshooting:

my app uses the command line keys to over ride any lua settings, there are settings for VR Enabled in the options.lua so if you goto DCS Settings and enable VR and relaunch, it saves in the LUA as VR Enabled = true.

the only thing my launcher does w/ the launch VR On / Off Command buttons is bypass the ED Launcher.

figured as the compare show the only line difference was: creators[devices.HELMET_DEVICE] = {"avNightVisionGogglesV2"}

Well I was close, cause I was in devices.lua editing some things.. Which part the sub/secondary indicators for the HELMET_DEVICE? I'm gonna have to run them through compare and check now...

Visor Function isnt in the Lua code from what I saw.. as far as the pages, the MUMI Page didn't change with this patch.. It likely changed w/ the patch before it.

You wont be able to add any new weapons, The systems for player cockpit are set to detect CLSIDs of the weapons and load the necessary interfaces per hardpoint.

Canopy icing is modelled in the 3d model.

I am working on updating a few under the hood changes, progress is slow due to job requiring me to leave for remote locations where internet is often non-existent, as well as closing on a new home. I'm still also trying to fully traceback and eliminate some multi-threading desync/permissions issues w/ some of the scanning functions. Current Hill's assets are in game content, integrated into the game. Prior they were a mod, that's still in game content via module that uses DCS Modulization infrastructure. My Launcher is an external application, and doesn't fully integrate with any DCS functions at all, so two entirely different scenarios, however, one could use my launcher regardless of DCS version and bypass the built in ED Launcher if they choose.

I am currently working on other projects, hopefully this winter I can resume working on the planned "F-5E: Expansion" Modules. Core AI, Player FCS and Player DCS Are planned for the first release, after which the Player Remastered version, if at all, due to models being encrypted. Since putting it on pause I've learned several new things that will aid in quicker turn around on getting this project done quicker and cleaner.

F-16C Core Avionics were changed significantly over the last few patches w/ the addition of SniperXR, DTC, DL, And more in depth MFD Pages etc. As well as additional animations for cockpits and pilots, It's likely both the 3D Model Animations and Cockpit systems scripts would need an extensive overhaul.

null

It's either the C-130 Mod or the Armed black hawk: Explanation: The reason the C-130 causes DCS to have a stroke when CJS Module is installed, is because the ordinance table is built using the new database names ie ("Weapons.Missile.AIM_120C") etc etc. and when the C-130 Mod tries to build it's ammo crates using a wstype that's a mixed string (integer and table name), DCS has already processed the CJS Ordinance table and shifted the database to the Type.SubType.Unit format, and therefore the wstype string containing both integers and table name is no longer valid, plus the weapon is already defined, as the CJS Mod Tells DCS to Process the Aircraft Weapons Pack first. For the C-130 Mod, the Problem line in the loadout lua file is 180 Ammo_Pallet_Contents({user_name = _("Ammo GBU-31V3B*6 [12949lb]"), clsid = "Herc_Ammo_GBU_31_V3B_bombs", contents = "{GBU-31V3B}", count = 6, mass = 981, wstype = {4, 5, 36, GBU_31_V_3B}})--GBU-31V3B The DCS Core function calls for a wsType of either 4 Stage numbers or the new format of 3 stage definitions, This line calls for 3 stage numbers then a table name, which DCS see's the table name as invalid due to a weapon already being declared using weapons.bombs.TABLE_NAME. So the Fix is to update the weapon wstype in the pallet's wstype, you can update it to use the new weapon wsType format: Ammo_Pallet_Contents({user_name = _("Ammo GBU-31V3B*6 [12949lb]"), clsid = "Herc_Ammo_GBU_31_V3B_bombs", contents = "{GBU-31V3B}", count = 6, mass = 981, wstype = "weapons.bombs.GBU_31_V_3B"})--GBU-31V3B

Chin Sensor on the Tomcat was trash, which is why it only lasted for a few LRIP runs of the A before being replaced by the TCS, The manufacturer touted an updated version, and it was added as a dual Chin Pod for the D, but was pretty quickly aerodyn covered off as they failed, or just left defunct.. Both cases and the IRST21 in the ASG-34A / FPU-13/A Tank, were the USN trying to add something to counter what Russia had, the Passive detection on the Mig-29s and Flankers. But face it, the system was better designed and implemented on those. slapping a cheap IR Sensor on the bottom of the chin or on the nose of a fueltank underneath the aircraft, makes it nearly impossible to detect anything above the horizon / nose line of the aircraft. and both configurations are at risk of ground debris damage