Jump to content

SkateZilla

ED Beta Testers
 View Profile  See their activity

  • Posts

    21642

  • Joined

  • Last visited

  • Days Won

    20

 Content Type 

Everything posted by SkateZilla

  1. SkateZilla
    definately on my whiteboard list, as my mouse has developed an unwanted random double click symptom.
  2. SkateZilla
    - 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:
  3. SkateZilla
    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.
  4. SkateZilla
    the only thing my launcher does w/ the launch VR On / Off Command buttons is bypass the ED Launcher.
  5. SkateZilla
    figured as the compare show the only line difference was: creators[devices.HELMET_DEVICE] = {"avNightVisionGogglesV2"}
  6. SkateZilla
    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...
  7. SkateZilla
    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.
  8. SkateZilla
    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.
  9. SkateZilla
    Canopy icing is modelled in the 3d model.
  10. SkateZilla
    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.
  11. SkateZilla
    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.
  12. SkateZilla
    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.
  13. SkateZilla
    null
  14. SkateZilla
    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
  15. SkateZilla
    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
  16. SkateZilla
    it'd be pretty weird because none of the tankers have the same light array layout.
  17. SkateZilla
    While the fuel will be usable in DCS, the sensor wont. But that being said, even Block II of this pod has been a rough development,... Ya know we told them not to put a sensitive optical sensor immediately behind the nose gear.... but do they listen? nope. Pay Attention to the STA (Station) Prefix in the description.
  18. SkateZilla
    that eyeball has a high maintenance and failure rate due to the design.
  19. SkateZilla
    well the ASG-34 IRST21 is Technically a Tank w/ an Eyeball.
  20. SkateZilla
    USN Never Flew w/ the Fairings, as they didnt purchase them, they re-used the launchers, but did not elect to pay for more covers.
  21. SkateZilla
    They are AN/ALQ-249 Next Generation Mid-Band Jammers.
  22. SkateZilla
    When choosing loadout stores, pay very close attention the the [ STA xx ] Prefix of each store's description. Since the PSM of the Charlie is only modelled for 9 Pylons and 1 internal auxiliary store location (ie for Smoke Generators), There's a lot of offset or split stores in the list.
  23. SkateZilla
    This is fixed internally, once the latest build passes some testing phases and I remove some things that aren't released, then the public will have a new build.
  24. SkateZilla
    I have a Model of the Pylon, however Fuel tanks cannot have 2 element attachments, so I cannot place it like I would a Missile using a Launcher. I'd rather replace the entire external for A/B and F
  25. SkateZilla
    The Pylon is integrated into the F-5E Model, I cannot move it. The only way would be to replace the model w/ a new one that I can edit. I have other projects that are higher priority at the moment, plus I still have to do a separate version of everything for the F-5E Remastered Version, as the model is not the same and Items don't line up correctly.
×
×
  • Create New...