Jump to content

Bones1775

Members
 View Profile  See their activity

  • Posts

    185

  • Joined

  • Last visited

 Content Type 

Everything posted by Bones1775

  1. Bones1775
    these are the differences i found in device_init. left is the ed file right is the mod file i have been using
  2. Bones1775
    Unless i had an older version of the file there were 2 lines missing from the mod file that were in the ed file. One regarding tgp and the other regarding rwr. And 2 lines added regarding the code you posted. Also the devices.lua needed edited to maintain the original file sequence.
  3. Bones1775
    Compare is how i found the fix. I am not a coding guru so i couldn't figure a way to keep the nvg function. Hope you coding gurus can figure it out.
  4. Bones1775
    There was a couple lines of code that needed added to the mod that has been added since the mods last update, this fixes the alr-67 issue. The lines that were added to the mod regarding helmet device need removed to restore visor function. This is what adds the nvg to the jhmcs. Obviously removing it you gain visor function but lose nvg with jhmcs.
  5. Bones1775
    I found the problems and fixes, both in the device_init.lua. sent to capt coke. Unfortunately the fix removes the nvg use with the jhmcs.
  6. Bones1775
    With the latest patch 10/22/2025 this mod breaks the ability to load the ALR-67 partition on the mumi page as well as breaking the new visor function.
  7. Bones1775
    can we get a hornet special options check box to remove or apply the tinted HMD visor?
  8. Bones1775
    thanks, based on my experience with the hornets rwr export the changes that will need done to make them readable will make them unreadable in the cockpit but i'll be doing some testing with it later today. basically need to find where it defines the line weight and fuzziness for the displays part 2 got it, you need to edit the following file VNAO_T45\Cockpit\Scripts\materials.lua. (line 21) MFD_thickness = 0.2 i used the following MFD_thickness = 4.2 see the attached screenshots to see the results. as you can see it does make the in cockpit displays unreadable. you can mess around with line 21 and 22 to get the desired effect that suits you.
  9. Bones1775
    what did you have to change to export?
  10. Bones1775
    if you make it black you wont be able to see it at night
  11. Bones1775
    And 59 is automatically programmed to bullseye
  12. Bones1775
    I am curious why we can't control our wingman data link wpns and if this feature will be added in the future?
      • 6
      • Like
  13. Bones1775
    getting reports from squadron members that todays patch broke this mod. makes sense, we did get a new ddi page today.
  14. Bones1775
    i do but i have tried with and with out them in the export lua. have gone as far as deleting everything in the scripts folder and letting winwing replace their required files. it has worked a few times but it never works o a restart of the game and i can find no rhyme or reason why it worked the few times that it did.
  15. Bones1775
    no i mean the displays on the UFC do not show what is in game on the UFC. i am not talking about the MFD exports i'm well aware of the issue with them being dimmer and for that matter the in game one being too bright when they are exported.
  16. Bones1775
    i recently bought the MIP and was finally able to get it set up in game. Unfortunately, the LCDs and light very seldom sync with the game. i think it has been a total of 3 time over the past day. i have done the lua repair, deleted everything in the export folder and restarted SimAppPro to no avail. it is quite frustrating. when it has worked i exited the mission(the LCDs retained what ever info was on the UFC) and restarted and it no longer synced. the reset lights check box is selected. Anyone have any idea what could be interfering with the syncing?
  17. Bones1775
    did some comparing of lua files and there have been a lot of changes to the formatting of some of the code. most likely the culprit in this. i'm personally not smart enough to figure out how to fix it.
  18. Bones1775
    can we get clarification on how anchor point works. what is the pattern off the base point. my orbit tracks are off from what i would expect.
  19. Bones1775
    has anyone experienced this in an air start jet. all my LTD/R CTD have been cold starts.
  20. Bones1775
    here are my track files. default FMU-140 fuze settings used. FMU-140 VT1.trk FMU-140 VT2.trk
  21. Bones1775
    i think they have something backwards from what i just read in the doc i found. it does have 2 settings VT1 and VT 2. in the jet VT1 gives you the option to set HOF but the bomb dispenses right after release. VT 2 does not allow you to set HOF but the bomb does appear to use the prox fuze. but since you can't select the HOF it is not accurate
  22. Bones1775
    @Massun92 certainly, i'll DM you the details later today.
  23. Bones1775
    @Massun92 May i make a suggestion, in your DB files you have the shape and textures mounted in the individual unit lua's. you can remove them from there since you also have them in the entry.lua. As such the DCS log is throwing warnings for them already being mounted. (ie. shapes is already mounted to the same mount /models/.). I have been editing them locally to clean up the log for myself and thought it would be a good idea to bring it to your attention. great mod and always looking forward to the updates.
  24. Bones1775
    Can you set altitudes in the B and C routes
  25. Bones1775
    Guard Receive does not appear to work. i have a mission set to broadcast a sound file over the guard frequencies but i can not here it in the strike eagle when guard receive is selected. if i dial in the frequency manually i can here it.
×
×
  • Create New...