Jump to content

hlfritz

Members
  • Posts

    196
  • Joined

  • Last visited

Everything posted by hlfritz

  1. We noted that the barometric pressure setting was abnormally high on the Gulf mission, 31.5 or so. This is not within the normal ranges of barometric pressure found here on earth. I changed it in the ME to be 30.3, slightly high of norm for the fair weather in the mission. It being abnormally high means some aircraft cannot adjust their settings to read 0 altitude at sea level. Edit: reset it to 29.92 as it seems the Hornet cannot adjust above 30. also, since we are doing hot starts (limited game time) the altimeter may not get adjusted properly during that simulated start.
  2. OMG - they did it AGAIN? I thought it was curious as Clearfield still works fine. Any chance you plan to fix, or are you fully invested in Escalation now?
  3. Is anyone having issues running this mission recently? We finished it in the fall, and decided to restart it again a couple weeks ago. No red air, it seems the MOOSE DOOM AI A@A dispatcher is no longer functional with some updates in DCS perhaps? We were running a customized mission, but I just tested with a stock version 1.29 and get the same issue, same message in the server log: 2021-01-02 02:42:02.611 INFO SCRIPTING: *** MOOSE INCLUDE END *** 2021-01-02 02:42:02.686 ERROR SCRIPTING: Mission script error: [string "C:\Users\RLG\AppData\Local\Temp\DCS.openbeta_server\/~mis00005690.lua"]:114528: attempt to index field 'Airbase' (a nil value) stack traceback: [C]: ? [string "C:\Users\RLG\AppData\Local\Temp\DCS.openbeta_server\/~mis00005690.lua"]:114528: in function 'SetSquadron' [string "C:\Users\RLG\AppData\Local\Temp\DCS.openbeta_server\/~mis000074F6.lua"]:212: in function 'SEF_REDSQUADRONSMULTIPLAYER' [string "C:\Users\RLG\AppData\Local\Temp\DCS.openbeta_server\/~mis000074F6.lua"]:594: in main chunk I get a similar or same error in the server log if I check defense networks, for both blue and red. I can provide exact if necessary. I suspect something changed with recent DCS updates perhaps.
  4. been a while, i am wondering if this is still an issue? i noted over the last few weeks on the rare occasion i get to land and rearm/refuel for another mission i do not have a brake chute for my second landing. is it still only replaceable with a repair? i also checked the ground crew menu and saw nothing there either? i found something potentially related - air. is there an air tank that needs to be refilled with rearm and repair, and do i need to do something to ensure it is filled after a landing (i saw something about a switch to put it back to center after landing, before rearm and repair)? thx!
  5. Surrexen, It is the areas to call support to. I.e. call in fighter support, work your way down the menus, and finally get to a destination. Some of these support areas are just not on the map. I may have figured some of it out though. They all seem to be airports/airfields? However, not all show on the map. Is that because some of them are owned by red coalition? Is that intentional (i.e. red airfields do not show on map)? The other concern is that if there are a lot of units around the airfield its name cannot be sorted from the units, also not allowing one to see/find it. Also, some of the destinations for support call are extremely close to each other and they seem pretty redundant. I.e Ramat David and Megiddo are extremely cloe and probably do not need to be separate destinations for support aircraft to be called to.
  6. Geography lessons aside - the areas called out for support mission target areas are not on the map? If they were, it would be far easier. No help here?
  7. Hey Bro, thank you for doing this! Any chance for hints on where all of thee sectors are for calling in support? I will say many of us are probably not familiar with these locations and I know I personally have no clue where the sectors are. Thx!
  8. Concur, our group did this earlier this week! Mirage 2000 and F-14.
  9. It has a Paveway III guidance system attached rather than a Paveway II of the GBU-10/12/16 series. Rather than make on/off steering adjustments, it is able to make gradual/partial steering adjustments allowing for better trajectories, longer flights, and more accuracy.
  10. No way! :) I did not find it in the patch notes. Will check it out asap.
  11. @nighthawk, Not able to do anything for the GBU-24? thank you sir.
  12. nighthawk, hopefully you could do something for the gbu-24. it would be great.
  13. Nice to see you back mate! ;)
  14. well, it deals with weapons mod. Personally I think guidance is part of the weapons performance. I asked several posts up, refer to posts 74-78.
  15. well, the changes have definitely slowed down compared to 3 months ago. the issue with gbu-24 is not damage, it has no guidance in the game. while the F-14 and Mirage can carry it, it does not follow lasers as it should.
  16. I am also wondering, especially re: GBU-24. ;)
  17. It should only do that when your server updates. Alternatively, ensure your server is completely shut down before editing the file. Once edited, restart the server but check the file after you edited it to ensure it "stuck". If it did not, you may not have write permissions to the files location and need to correct that as well.
  18. You can change the spawn intervals of each of the enemy cap flights already. This will not necessarily make a pause between waves, but can slow down the frequency. You can even comment out some of the enemy cap flights altogether if you want. This in done in the air defense script included within the mission itself. So, really, it is already there. You will just need to be comfortable with code/scripting.
  19. Thank you. So yes, as I suspected due to adding all those other axis. Why not just keep the same ID's for the throttle and brakes and make the new axis the new IDs? Failing the ability to do that (why are you not able to do so?) how about a better warning (post in the forums maybe?) and workaround rather than just one line in the release notes and saying you have to remap your joystick? Please? You guys (Deka) are so awesome at this stuff so far.
  20. No, I tried rebinding in the UI interface. No go. I deleted what was there and did the rebind thing. It detected the axis, but thrust did not work. I will look at the lua file when I get a chance, but I am a bit miffed that it does not work and I could not fly the Thunder in our group session last night (because of course I did not know it was not going to work after the update). I would really like to understand why this change was made. Something to "fix" the ID's.
  21. Thx, yes I saw that from uboats posts on the subject. While I might get some time to edit the lua file, I do NOT have time, nor should I have to, remap my entire throttle. I am asking what happened to the JF-17 throttle here? Other modules still work fine as I noted. Will there be a hotfix to reverse this issue? EDIT: Is this because of all the new axis that were created for the jet? EDIT 2: Wait, I see that in the notes we HAVE to rebind our joystick?!!!! First, I think this is meant for throttle device since the wheel brakes and throttle axis were "fixed". They worked fine before, what was fixed? And wow, one small line in the notes to state that we must rebind? That is generally a huge effort for a lot of people. I personally have very little free time, and now I have to spend it rebinding the throttle device? Or maybe just fly other jets... Arrgh.
  22. I also have an issue with throttle after update. Other modules still work fine, but the JF-17 throttle axis does not work. I also noted that each controller had the default mapping of joy_x (I believe that is correct) and I know I have deleted those default mappings. I then deleted these mappings in the interface and remapped it on my throttle - still a no go. What happened to the JF-17 throttle axis?
  23. agreed, health is far more important than this. just leave it until you are well enough to get back into it.
  24. Ah, so I am not the only one! I am glad to hear that, I mean for me - not for the mission! ;)
×
×
  • Create New...