Nightstorm

This looks awesome. Thank you for sharing this with the community!

I had my ride removed from underneath me by a Gadfly just last night. I definitely had the RWR warnings.

Yes that is true for version v2.5.6.49798 and earlier. After that version which was from back in July '20 the DLL files required that you refer to were encrypted and the aircraft was no longer flyable. That's why the changes I've made no longer require the dll file and it is flyable again but it's missing some of the functionality that the dll file provided. There is at present no other option for any version after v2.5.6.49798.

I've created a mod out of this for those that would prefer it. The zip file contains stock input files for the Viper with only the new commands added under the systems section. The new commands can be located under the -- Ejection Seat Lever line in the lua files. Input.zip

The smoke looks very very authentic. I had other modded files in place before but replaced everything with your versions and I was very impressed with how good this looks. Nice work sir.

Never mind. I found it. The new files appear to be common for all aircraft that have the M61 cannon. \Saved Games\DCS\Sounds\sdef\Weapons\M61Cannon_In.sdef & M61CannonEnd_In.sdef \Saved Games\DCS\Sounds\Effects\Weapons\M61Cannon_In.wav & M61CannonEnd_In.wav

While the new F-16C Vulcan cannon sound is pretty nice and a significant improvement over the original, I was using a custom accurate sound sample and with the new version my modded one is no longer used. The path to my custom ones remains unchanged; \Saved Games\DCS\Sounds\Effects\Aircrafts\F-16\Cockpit\VulcanIn.wav \Saved Games\DCS\Sounds\Effects\Aircrafts\F-16\Cockpit\VulcanEndIn.wav So the new effect must be using a different name. Can anyone tell me what that new sound name is or how to determine that? Thank you!

Not a mod exactly, but here are instructions to add the commands to make the Viper's seat arming handle bindable to controls. You'll want to add the following lines to two files located here: Mods\aircraft\F-16C\Input\F-16C\joystick\default.lua Mods\aircraft\F-16C\Input\F-16C\keyboard\default.lua ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- Ejection Seat Lever { down = cpt_commands.EjectionSafetyLever, cockpit_device_id = devices.CPT_MECH, value_down = 0.0, name = _('Ejection Safety Lever, LOCKED'), category = {_('Systems')}}, { down = cpt_commands.EjectionSafetyLever, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Ejection Safety Lever, ARMED'), category = {_('Systems')}}, { down = cpt_commands.EjectionSafetyLever, up = cpt_commands.EjectionSafetyLever, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, value_up = 0.0, name = _('Ejection Safety Lever, ARMED/LOCKED'), category = {_('Systems')}}, ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- They can really be pasted in anywhere but in my files, for the keyboard file I pasted these right before the line: -- EPU Control Panel For the joystick file I pasted them at the bottom of the systems section which can be found after the line: -- Systems ---------------------------------- You'll have three new bindable control options for your F-16 under the Systems category. Ejection Safety Lever, LOCKED (Seat Safe) Ejection Safety Lever, ARMED (Seat Armed, obviously) Ejection Safety Lever, ARMED/LOCKED (A toggle between the two for a single switch)

I figured out how to do this myself. You'll want to add the following lines to two files located here: Mods\aircraft\F-16C\Input\F-16C\joystick\default.lua Mods\aircraft\F-16C\Input\F-16C\keyboard\default.lua ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- Ejection Seat Lever { down = cpt_commands.EjectionSafetyLever, cockpit_device_id = devices.CPT_MECH, value_down = 0.0, name = _('Ejection Safety Lever, LOCKED'), category = {_('Systems')}}, { down = cpt_commands.EjectionSafetyLever, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Ejection Safety Lever, ARMED'), category = {_('Systems')}}, { down = cpt_commands.EjectionSafetyLever, up = cpt_commands.EjectionSafetyLever, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, value_up = 0.0, name = _('Ejection Safety Lever, ARMED/LOCKED'), category = {_('Systems')}}, ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- They can really be pasted in anywhere but in my files, for the keyboard file I pasted these right before the line: -- EPU Control Panel For the joystick file I pasted them at the bottom of the systems section which can be found after the line: -- Systems ---------------------------------- You'll have three new bindable control options for your F-16 under the Systems category. Ejection Safety Lever, LOCKED (Seat Safe) Ejection Safety Lever, ARMED (Seat Armed, obviously) Ejection Safety Lever, ARMED/LOCKED (A toggle between the two for a single switch)

Yes. --mount_vfs_model_path ("Bazar/World/Shapes") --mount_vfs_texture_path ("Bazar/World/textures") Those seem to be the lines causing the incompatibility with the F14A. And commenting them out doesn't appear to affect them.

As far as I know the ones that were updated were the SFM versions. However, the culprit lines appear to be these in the entry.lua file: mount_vfs_model_path ("Bazar/World/Shapes") mount_vfs_texture_path ("Bazar/World/textures") Comment those out and everything seems to work.

It'd be great to have controls for the Ejection seat arm and disarm that can be bound.

See page three on this thread: https://forums.eagle.ru/forum/english/licensed-third-party-projects/heatblur-simulations/dcs-f-14a-b/bugs-and-problems-bf/7143465-ctd-with-the-f14a

See this thread: https://forums.eagle.ru/forum/english/licensed-third-party-projects/heatblur-simulations/dcs-f-14a-b/bugs-and-problems-bf/7143465-ctd-with-the-f14a Solution is on page 3. New versions of VSN mods are available for download as well.

Awesome thank you. I made the same adjustments to the Superhornet files after comparing versions of the VSN_F35 entry.lua to see what you changed. Worked like a charm. Everything is back to 100% functionality. And the F14A is working great as well. Thanks again!

Thank you! This works great, and I used the changes you made for other mods to make them compatible as well. Much appreciated :)

https://forums.eagle.ru/forum/english/licensed-third-party-projects/heatblur-simulations/dcs-f-14a-b/bugs-and-problems-bf/7143465-ctd-with-the-f14a?p=7145390#post7145390 The Heatblur folks are willing to help find a solution :)

That's awesome to here IronMike. Thank you. I'm sure in that case a solution will be found.

If it's of any help...every crash shows an "Access Violation in the F-14 Avioncis.dll" I attempted to use a version of the VSN F-35 mod that uses the SFM and doesn't call any core files like the F15.dll that the old version used. And the crash still occurs. I completely understand the point of views that have been expressed. "3rd party devs can't be responsible for mod compatibility". However, any help in identifying why these certain mods are causing incompatibility would be appreciated :) # -------------- 20201119-182721 -------------- DCS/2.5.6.57949 (x86_64; Windows NT 10.0.19042) F:\DCS World OpenBeta\Mods\aircraft\F14\bin\F14-Avionics.dll # C0000005 ACCESS_VIOLATION at E514451D 00:00000000

It would appear that *some* 3rd party aircraft mods will work. I don't know why. Several VSN aircraft and the Super Hornets all cause issues. Not only do they cause a CTD if you attempt to fly 14A but if you place it in a mission as an AI controlled aircraft the mission will work but it's the wrong version of the F14A. And the one I selected is the yellow flyable one and I'd removed the VSN_F14A just in case of a conflict. I have no idea why this is happening but it won't work for example with only the VSNF35 installed. I use that aircraft in many missions. So.....until or unless this is fixed, the F14A doesn't exist in my DCS. The F14B seems to work just fine.

Here's the stock files with only the lines needed for the lights changed. The changes are tagged with --NIGHTSTORM so you can find them easily if needed. To be clear, this wasn't MY mod, I'm just using what I learned from it to modify the stock files every time there's an update ;) Strobe Lights.zip

You're welcome. Let me know if you've got any issues. I could always share the lua files.

Ironically there was so much traffic generated by posting this that Dropbox suspended my public downloads and wanted me to "upgrade". So if it's not working, just give it a bit.

I use this all of the time for the Viper and Hornet. I've combined it with other mods like the smoke mod or Blue Angels equipment etc. It's a modification to a couple of lines in the lua file to make it work. I'd suggest using Notepad++ it's a free editor. Make a backup of your F-16C.lua located in \CoreMods\aircraft\F-16C and your FA-18C.lua located in \CoreMods\aircraft\FA-18C as needed. Search the file you intend to mod for these lines: F16 - lights data STROBES section { typename = "argnatostrobelight", argument = 193, controller = "VariablePatternStrobe", mode = "1 Flash", period = 0.500, }, Replace with these: { typename = "natostrobelight", argument = 193, controller = "VariablePatternStrobe", mode = "1 Flash", period = 0.500, color = {0.9, 1, 0.7}, position = {-6.5, 2.87, 0.0}, intensity_max = 75}, Next the -- STROBE / ANTI-COLLISION section: Find the line: { typename = "argnatostrobelight", argument = 192, period = 0.4, flash_time = 0.1, }, Replace with: { typename = "natostrobelight", argument = 192, period = 0.4, flash_time = 0.1, color = {0.9, 1, 0.7}, position = {-6.5, 2.87, 0.0}, intensity_max = 75}, F16 Done. For F18 - Fine the line: { typename = "argnatostrobelight", argument = 193, period = 1.2}, -- beacon lights Replace with: { typename = "natostrobelight", argument = 193, period = 1.2, color = {0.8,0,0}, intensity_max = 73, position = {-5.32, 2.58, -1.81}}, -- beacon lights F18 Done. That's it, now you'll have the strobes on each aircraft. White for the Viper and Red for the Hornet.

I assumed as much regarding the DLL file. I do understand that it's not a good flight model using SFM and it's not even remotely realistic by comparison to the F22. None the less, it's a great 3D model with a great 3D cockpit that does put you in the Raptor. I spend most of my time in full fidelity modules, however, sometimes I like to just buzz around in something that at least looks like an F22 even if all it can do is employ air to air weapons. In this iteration for the current open beta you can use the RADAR, you can lock and fire AMRAAM's on targets and fly around in what looks like a Raptor. You can navigate with the HUD and waypoints as they work. The engine display works and the message center works. None of the other pages work as indicated but it can still be fun. Yea, you can't tell how much gas you have but you can guesstimate and if you're wrong....well....when it gets quiet all the sudden it might be time for a change of scenery. I for one am glad you made this mod and that it still works even in a limited capacity. I have an install of the old Stable on my PC just for this and other mods that relied on ED DLL files. I just wondered if it would work at all with an SFM and it does. I made a bunch of liveries for it as well, something approaching 2.5GB worth compressed. I didn't upload those as they were all made with the PSD I included. If there is interest I can. I understand that you don't want to support this any longer and there of course is no obligation. If you want me to take this down let me know. Thank you!