cj43g3r

@avgyst, when i initially received my AB9 it would randomly either fail to connect at power on (button) or disconnect some short time later (usually between missions). It had outdated firmware from Sept 2024 (1.1.1.26) but Moza Cockpit would repeatedly fail at attempts to update the AB9 firmware to the latest as of Jan 2025 (1.1.1.32) until the AB9 was removed from Windows device manager and the driver reinstalled.

To fix incompatibility with CH47 Chinook mod, modify Saved Games\DCS\Mods\aircraft\CH7 Chinook\FM\Ch47_Chinook_config.lua as: nullnullnull To fix incompatibility with CH53 mod, modify Saved Games\DCS\Mods\aircraft\Sikorsky CH-53E Super Stallion\FM\CH_53_config.lua as: null To fix incompatibility with AH-6J, there are files missing in AH-6J v3.5 and v4.0 null Extract v4.0 on top of v3.5 on top of v2.0 (https://www.digitalcombatsimulator.com/en/files/3314815/)

I've created moza cockpit 1.0.3.9 compatible presets at https://www.digialcombatsimulator.com/en/files/3343585/ When I upgraded from moza cockpit 1.0.2.14 (standalone installer) to 1.0.3.9 (web installer) it was missing the preset for the F-14B and I found out the presets files were not compatible between these versions. I created the F-14B preset by exporting the F-4 preset from 1.0.3.9 and copying the corresponding values from the F-14B preset from 1.0.2.14, giving it a unique uuid. I used the F-14B as a template for creating additional presets using chatgpt. e.g. creating the F-15C preset: Open the F-14B preset with a text editor, select all, copy, and then paste the contents into chatgpt prompt. At the chatgpt prompt: This is a moza force feedback joystick preset for the F-14B Tomcat in json format. Using the F-14B preset as a template, can you create a preset for the McDonnell Douglas F-15C Eagle using publicly available information. I noticed that chatgpt has a tendency to remove settings if they are unused for a particular aircraft but it does not seem to affect moza cockpit. If you want to retain all settings then you may want to change the chatgpt request to something like this: Using the F-14B preset as a template, can you create a preset for the McDonnell Douglas F-15C Eagle using publicly available information keeping all unused settings. I have no idea if these presets are accurate. They can be considered a best guess providing aircraft with different characteristics until moza releases additional presets. chatgpt randomly inserts the aircraft manufacturer, name and model in the preset name or leave one or more missing. it also automatically generates a unique uuid. After importing the preset into moza cockpit, you may need to select a DCS vehicle and enable auto matching or manually load the preset if there is no matching vehicle. Some mods might not support FFB, so under basic settings for the preset you may need to choose telemetry FFB or integrated FFB. The F-14B preset was likely configured without a joystick extension, so the others will be the same. Feel free to modify and redistribute them.

@Archangel44 Regarding the F15C dependency, see I've created a tool to simplify this at https://www.digitalcombatsimulator.com/en/files/3340679/ It doesn't solve all issues related to upgrading to FC2024 but is a step in that direction. Regarding the FPS, it is a hardware performance issue where the mod is attempting to render a "fisheye" view in the cockpit. See whiskey.actual's post on April 5, 2023. If you're using VR, you can try head tracking vs VR to reduce performance hardware requirements. You can also try reducing the game resolution, DCS visual quality under options/system (especially forest details factor/scenery details factor) to reduce the workload. You can try disabling unnecessary windows services to remove resource usage and processor load. I don't know if you've optimized your system. But enabling resizeable BAR in the UEFI/BIOS is a way of increasing GPU performance. And reducing competing CPU resources by disabling CPU affinity for CPU0. e.g. Unselect CPU affinity for CPU0 for DCS, head tracking software (e.g. opentrack) so that they will run on other CPUs. CPU0 will have a lower load and more time to process interrupts since it seems many interrupts are just assigned to CPU0 by default. This seems to significantly reduce mission load times on my system

@sBryansGames Only at the specific location in FC3 aircraft entry.lua. Please refer to SkateZilla's August 16 post in this thread.

Reviewing this entire thread, Urbi found the solution on 12/23/2023 for spawning carriers. See RaptorFighter's post on 12/23/2023 To make the solution more clear, modify the following files: "%USERPROFILE%\Saved Games\DCS\Mods\aircraft\JAS39\Weapons\jas39_dws39_arm.lua" line 188 from cluster = cluster_desc("Bomb_Other", wsType_Bomb_Cluster, to cluster = cluster_desc("Bomb_Other", wsType_Bomb_Cluster, levParam), "%USERPROFILE%\Saved Games\DCS\Mods\aircraft\JAS39\Weapons\jas39_dws39_tv.lua" line 188 from cluster = cluster_desc("Bomb_Other", wsType_Bomb_Cluster, to cluster = cluster_desc("Bomb_Other", wsType_Bomb_Cluster, levParam),

In a process of elimination you can comment out the following 2 lines in "%USERPROFILE%\Saved Games\DCS\Mods\aircraft\JAS39\Weapons\Loadout.lua" so that carriers can spawn: e.g. -- dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_arm.lua') -- dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_tv.lua') it's not a memory limitation but an issue with jas39_dws39_arm.lua and jas39_dws39_tv.lua

@Hawkeye60 and @Marko1985 Thanks for the mods! I was wondering could you release the J-20 mod (https://www.dropbox.com/scl/fi/s2e1yyk6aitijf3yfnz0d/Chengdu-J-20-Mighty-Dragon-V2.8.0.rar?rlkey=nr9ii8i5jxhg7r8g2kllpdudk&e=1&dl=0) as variants with different engines (e.g. AL-31FM2, WS-10C, WS-15) even if only with publicly available data on military/afterburner thrust such as from wikipedia or other sources? In the chengdu_j_20.lua: thrust_sum_max = 8200, -- thrust in kgf (64.3 kN) thrust_sum_ab = 14276, -- thrust in kgf (95.1 kN) Is this intended to be for a single engine where the J-20 has two? I can't seem to match up the thrust to public sources. E.g. (1 lb-ft ~= 2.204622621 kg) where WS-10 30000 lb-ft afterburner ~= 66139 kg per engine

@meimingzi123456 Thanks for your mod! I was wondering could you release it as variants if only with the differences in publicly available military/afterburner thrust for the different engines (WS-13, WS-15, WS-19) such as from wikipedia or other sources? I see in the mod's current J-35A.lua thrust_sum_max = 15200, -- 推力（单位：kg） 推力总和最大值 thrust_sum_ab = 25000, Are these numbers intended for one or two engines where the J-35 has two? I can't seem to match it up with public data. The DCS units are supposed to be in kg-force where (1 lb-ft ~= 2.204622621 kg). The WS-13 is listed as 19000 lb-ft with afterburner ~= 41888 kg per engine.

@cubanace Great work! And thanks for all the time you put into this and your other mods. You mentioned you were physically modelling the engines/nozzles for the AL-51. In the future, can you provide the Su-57 as variants with different engines (e.g. AL-31, AL-41, AL-51) even if only using public data for military/afterburner thrust with the same current 3D model. it would provide a feel for what it's like to fly in and against each of them and make sense of how it relates to current events in the news.

It seems there was never a solution where the JAS-39C mod prevented the spawning of carriers since 2023. I liked to do a lot of carrier operations so I uninstalled it. I just reinstalled it and verified the problem still exists with the latest version of DCS so I checked the "%USERPROFILE%\Saved Games\DCS\dcs.log" which provided a hint to the cause of the issue: 2024-10-05 00:35:25.578 INFO APP (Main): MissionSpawn:spawnShips 2 2024-10-05 00:35:25.616 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M61_20_HE_gr 2024-10-05 00:35:25.638 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M2_12_7_T 2024-10-05 00:35:25.701 WARNING LOG (29364): 2 duplicate message(s) skipped. It seems the JAS-39C mod has too much variety of weapons where DCS has either only allocated a fixed amount of memory or a fixed number of array slots for them. It does not seem to be an out of physical memory. If you view the file "%USERPROFILE%\Saved Games\DCS\Mods\aircraft\JAS39\Weapons\Loadout.lua" you will see a lot of lines starting with "dofile": e.g. dofile(current_mod_path .. '/Weapons/Loadouts/jas39_m71ld.lua') dofile(current_mod_path .. '/Weapons/Loadouts/jas39_m71hd.lua')) ... dofile(current_mod_path .. '/Weapons/Loadouts/jas39_agm-65h.lua') There are too many of them preventing the carrier spawning. As a quick test I commented out approximately half of them. This allowed DCS to load the JAS-39C mod and also the F-14/F-18 instant action missions to spawn carriers. You should be able to fly the Gripen with carriers by commenting out the weapons you don't need. Precede "dofile" with two minus symbols (e.g. -- ) to comment out a line. e.g. -- dofile(current_mod_path .. '/Weapons/Loadouts/jas39_m71ld.lua') Since the removal of FC3 and introduction of FC2024, you will also need to the workaround described by this thread.

I've been using an older version VSN_F35_v2.9.2.103_FC3_EFM.zip with DCS 2.9.7.59263 and setting the FC3 entry.lua's with Skatezilla's fix Landing gear and tail hook seem to be working for carrier landings. Weapons (cannons and missiles) seem to be working. https://e.pcloud.link/publink/show?code=kZskhnZwioeCmgDRQuieiKYUdSfC84HFmhV https://filedn.eu/ldmvNCjOtAfkbhMFc1BTA2f/VSN_html_Links/VSN_MODS.html I've also been using Spino's F-15EX as well (different what if scenarios of F-15EX v Su-57)

I can use this mod with DCS 2.9.7.59263. I noticed an error in <Saved Games>\DCS\Logs\dcs.txt: 2024-09-22 01:24:15.390 ALERT Scripting (Main): loadfile: [string "C:\Users\cj43g3r\Saved Games\DCS\Mods/aircraft/SW_CORVETTE/Sensor...."]:71: unexpected symbol near '=' It seems to involve "<Saved Games>\DCS\Mods\Aircraft\SW_CORVETTE\Sensor.lua" line (71): DIY_RWR_A = For some reason the lua compiler/interpreter doesn't like the preceding blank line: }, DIY_RWR_A = { but accepts: }, DIY_RWR_A = { I used an online lua compiler to determine this (e.g. https://www.tutorialspoint.com/execute_lua_online.php) Great job! Really fun practicing deadstick landings and carrier pattern landings with these (even if they are not enabled for carrier landings).

I'm able to to use it with DCS 2.9.7.59263. I noticed an error in <Saved Games>\DCS\Logs\dcs.txt: 2024-09-22 01:24:15.590 ALERT Scripting (Main): loadfile: [string "C:\Users\cj43g3r\Saved Games\DCS\Mods/aircraft/Sikorsky CH-53E Sup..."]:5: '}' expected (to close '{' at line 1) near 'suspension' It seems to involve "<Saved Games>\DCS\Mods\Aircraft\Sikorsky CH-53E Super Stallion\FM\CH_53_config.lua" line (3): moment_of_inertia = {198000, 76162, 80778} --{6170, 28982, 33441}, --{198000, 76162, 80778}, which requires a a comma after the closing brace preceding the first comment (--), e.g.: moment_of_inertia = {198000, 76162, 80778}, --{6170, 28982, 33441}, --{198000, 76162, 80778}, likewise line (9): pos = {5.312, 0.102, 0} also requires a terminating comma pos = {5.312, 0.102, 0}, Great job on this and the CH-47 Chinook! Especially when practicing zero/zero landings and autorotation.

I'm able to to use it with DCS 2.9.7.59263. I noticed an error in <Saved Games>\DCS\Logs\dcs.txt: 2024-09-22 01:24:14.943 ALERT Scripting (Main): loadfile: [string "C:\Users\cj43g3r\Saved Games\DCS\Mods/aircraft/CH47 Chinook/FM/Ch4..."]:12: '}' expected (to close '{' at line near 'damage_element' It seems to involve "<Saved Games>\DCS\Mods\Aircraft\CH47 Chinook\FM\Ch47_Chinook_config.lua" line (3): moment_of_inertia = {198000, 76162, 80778} --{6170, 28982, 33441}, --{198000, 76162, 80778}, which requires a a comma after the closing brace preceding the first comment (--), e.g.: moment_of_inertia = {198000, 76162, 80778}, --{6170, 28982, 33441}, --{198000, 76162, 80778},

@Fab8ball The log only shows DCS starting. You need to provide a log containing attempts to start a missions with the affected FC3 modules or mods based on them.

@Fab8ball i tried the FC2024 Su-27/Su-33 from their Instant Action missions and didn't have any issue. the DCS log at %USERPROFILE%\Saved Games\DCS\Logs\dcs.txt may contain some clues Are you only setting it for the Su-27 or Su-33 or all FC3 modules? Are other FC3 modules affected? Are you running the latest version of DCS with FC2024, or an earlier version of DCS or FC3? Low disk space/memory? If reverting the changes to the entry.lua's and it fails integrity check, you can always perform a clean reinstall. If it's installed via Steam, you can use Steam to verify the game files were installed correctly.

I've been trying to learn to fly some helicopter modules and mods and this may help. In real flight videos, it involves very small movements to the cyclic of a long stick. Similar to flight demo teams such as the Blue Angels and Thunderbirds when flying in tight formation. Typically a slight squeeze in a direction. In contrast Hollywood movies show large stick movements for visual effect. Most DCS users will have a short joystick. A way to scale down the movements and simulate a longer stick is to add linear saturation to both the pitch and roll. For both pitch and roll, click on "axis tune", then set "Saturation Y" originally 100 to 30-50 and leave the other settings with original defaults. A setting of 50 desensitizes it to 50% of the original. At a setting of 50 an actual stick deflection of 6 degrees will be treated as 3 degrees. You don't want any curvature since deflection of an actual longer stick is linear without any curvature. Each module/mod has different sensitivity to pitch/roll. The rudder (joystick twist axis or pedals), collective and throttle should use the default settings. You may need to invert pitch, roll and rudder in "axis tune" depending on your joystick. The OH-6 mod has a red box at the upper left indicating detected stick position. Stick forward should move it up. Stick back should move it down. Stick left and right (roll) should correspond to the same direction. Likewise for joystick twist rudder. For pedals, pushing left pedal turns left and pushing right pedal turns right. Same direction as differential wheel braking. From the videos, you will always see a center stick. When holding the center stick the wrist is against the thigh allowing finer movement. This is where a pit setup may make the most difference. A sidestick or desktop center stick doesn't provide this unless you have some sort of wrist rest. Try putting the stick between your knees to simulate the actual stick position of a helicopter without any pitch/roll axis tune saturation. Lastly, use small gradual adjustments for stick, collective and throttle.

@flavnet I don't have the Codename Flanker mod but I would suggest checking for alternate joystick bindings for roll, pitch, rudder. Some mods use different flight models (https://www.digitalcombatsimulator.com/en/support/faq/general/) and may require different bindngs. Also check if it's been disabled by autopilot (altitude, course, pitch hold). If the keyboard commands work, then it may be alternate bindings. If they also do not work, it may be autopilot or something else entirely. Then you would need to test with a different aircraft or different flight sim/game. You can also check the joystick bindings under the mod's Input/joystick/default.lua or the joystick binding of the mod's FC3 module. GlobalFixForAllFC3DependentMods.7z is a 7zip archive. Use 7zip (https://www.7-zip.org/) to extract it. It contains a readme.txt with detailed instructions. Visual C++ Redistributables version 14.40.33810.0 https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 https://aka.ms/vs/17/release/vc_redist.x86.exe https://aka.ms/vs/17/release/vc_redist.x64.exe You will need to install one or both of these depending on which version you run. The Debug, Release folders contain the x86 versions. The x64\Debug and x64\Release folders contain the x64 versions. On Win11, launch a "Terminal". On previous Windows it's called "Command Prompt" or "CMD". change the directory using the cd command to the folder where you will run GlobalFixForAllFC3DependentMods then run the command: .\GlobalFixForAllFC3DependentMods.exe /MOD:FC3=1 it provides backwards compatibility for some mods but breaks integrity check since it modifies FC3 aircraft entry.lua if you need to restore IC, then run the command: .\GlobalFixForAllFC3DependentMods.exe /BAK=0 /MOD:FC3= As you can see it is not an entire solution since you may want to fly online with a mod without breaking IC. But it does provides an easy way to switch back and forth such as when DCS is updated to a new version or when you need to restore IC

@flavvnet That's why source code has been included with the build solution/project files as open source. You can download/install Visual Studio 2022 community edition for private/individual use and rebuild the binaries. Before opening the solution file with Visual Studio, you can inspect them with any text editor. Then open/rebuild the solution file (*.sln) and compare the binaries with the ones included with the archive. I wanted to create it using a Windows built-in scripting language (batch/powerscript, javascript, basic). Basic is being phased out and may not be supported much longer. Batch/powerscript and javascript had more limitations requiring installation of additional 3rd party libraries/components. Python/perl requires installing an additional interpreter and 3rd party libraries. There is always sed. And there is open source sed for native Windows and sed in the Windows Subsystem for Linux but it would either require installing open source sed or WSL, become familiar with linux and regular expressions. I wanted it to be as simple as possible with as few dependencies as possible to make it easier to use for as many as possible. It's designed to just do a simple string search for the binaries section and insert the set string or remove it. This way, anyone can modify the configuration via the iniFile without needing to rebuild each time to support changes in FC3 entry.lua's or add additional planes. I've licensed it as GPL3 requiring future modifications to also be open source. If source code is not provided in the package or the binaries built with the included source do not match the attached binaries, then do not trust the package. You also bring up a good point that has been mentioned before but flamed down. Trojans/malware can be injected via binaries which can be included in mods as DLLs. So far the only way to detect them is check the forums for users reporting any bad behavior. So far there doesn't seem to be.

It's a solution for not having to start the mission with the FC3 dependency module and then switch planes. You should be able to use the older mods as long as the mod's features is not dependent on something specific to FC3 that FC2024 no longer provides.

I've created a commandline tool with the same name as this thread, GlobalFixForAllFC3DependentMods, at: https://www.digitalcombatsimulator.com/en/files/3340679/ Special thanks to SkateZilla and countless others involved in debugging/testing to find a solution after many months. The utility does exactly as described in this thread for backwards compatibility with FC3 dependent mods and can also unset the entry.lua's for IC . It's very extensible via an iniFile configuration in case of changes to the FC3 modules or additional plane mods built upon FC2024