DP Spaz

I fly the T-45 regularly and have done many traps, not had any issues catching a wire. There has been an occasional bolter, very infrequent and would contribute that to my approach rather than an issue with the mod. There should not be any difference between aircraft with the IFLOLs, and have not noticed any in the aircraft I flown. I will say that I've observed at times the IFLOLs does not seem to match where I touchdown on deck, similar to what you are saying, this has been in the Hornet. It does not occur frequent enough for me to start really looking at this in detail.

Yeah, had I opened my eyes a bit wider, maybe I would have seen it. I really appreciate your help!!! I've worked some with this mission editor, not nearly like I have with IL-2, which I'm very comfortable with and have created some very kool missions! I'll keep working with this mission editor, and I'm slowly learning MIST... as I use the script ciribob created for my range practice. I would love to add smoke markers to the bomb hits... MOOSE is the only way I know that's been done... well out of reach for me right now lol. I've updated that specific mission with this change, and also pulled in the trailing Burke in to 1.5nm from the carrier. I saw a few downloads of the file, so maybe other may be interested in it. I've also attached my evening field carrier landing practice mission (FCLP) that makes use of the Navy Equipment mod which is really awesome! I sure wish the portable IFLOLS was working, thrilled that they got the lighting fixed as I've been using this to practice my low light approaches. I am very regimented, and use this often to prepare for going to the boat! Guess thats the Naval Aviator in me When VNAO release the T-45, that was a huge gap filler in Naval Aviation Flight Training. If we can get the protable IFLOLS working, then we are about complete. I did notice that when you change tail numbers on the T-45 with the VX-23 skin, the tail number does not change in the game. Not sure if that was coded in or something missed. Thanks again!!! Spaz Causacaus CVN71 CQ.miz Spaz PG Eve Tunb Kochak FCLP.miz

Ah... something simple yet elusive... thank you very much! Makes sense now as the Burke behind is that distance. Appreciate your help and identifying the problem. I knew it had to be something simple. This particular mission I mod'd from my friend specifically to practice CQs... the other mission its working I created from scratch. Good to know this little detail... save headaches down the road!!! Again thank you very much!!!

I have looked at this mission, no success identifying the cause of the TACAN error. This mission was created before the release of the T-45 and was added to it after its release. As mentioned, I have another mission, the TACAN reports correctly. Maybe you can identify the cause. Thanks! Spaz Causacaus CVN71 CQs.miz

I verified that WP0 for the carrier has the same speed assigned as WP1 in the mission the T-45 is showing the incorrect TACAN distance. There are also Hornets in this mission, they show the correct TACAN distance. You have given me an area to investigate, so will keep digging to find the root cause.

Still seeing a TACAN issue with v1.01. An existing mission sitting on the CAT onboard CVN-71, the TACAN reads 2.2nm... and the distance changes once you launch. I tried deleting the T-45 and re-adding it, no change. A new mission with CVN-73, I do not see this issue, the TACAN is reporting accurately. Anyone else seeing this?

BlackLibrary, I really appreciate your work with the Navy Equipment.. it's awesome! And thank you for continue to support the mod, that's more awesome! I was pleased to find an updated version! I'm happy to report the the light-box is working just fine for DCS Open Beta 2.7.1.6709. I have a training mission for FCLPs, and your mod really adds to the realism and training. The evening mission is really sweet with the lights working! Hopeful that a solution will be found to get the meatball working. As a Naval Aviator, I would love to see a complete package in the training environment! I really applaud your work, and VNAOs on their T-45, 2 pieces that were badly needed for a Naval Training Environment! Wish I was able to help with the meatball problem, unfortunately I have zero knowledge creating mods. I am trying to learn MIST and identify a fix for the range script, that's slow in coming. Thanks again!!! Spaz

Thanks for posting, at least I'm not the only one having issues. We are having various issues with the script, some of which doesn't make sense as some times they occur, and sometimes don't. Earlier this week we were doing multiplayer, for the very 1st time my co-flyers callsign showed up when the script reported him on the range... that is the 1st time I've ever seen a callsign report. Normally its "noname". At this point I'm still not too knowledgeable yet on MIST, but working on it.

Flappie, this appears to have resolved the issue... from a fresh reboot, 1:03 to from start to the main DCS menu. Exit and restart the game, 0:57. I will continue to monitor and post an update if the issue returns. Thank you very much!!! Spaz

Merci Flappie for getting back with me so quickly. I have verified my capability mode is disabled... however, I did look closely at my dcs.log file and found 5 items that were taking longer times to load than others... ~20 secs for each... so I moved them from the game directory to my desktop and restarted the game... the results are below. Note, I did not have any issues with the previous version, and my other games.... XP11, MS2020 & IL-2 Sturmovik perform without issue or degradation. One other note, I cleared out my Windows TEMP files yesterday and saw load times return to ~1 minute to the main DCS screen. That has since gone away and now seeing 3-4 mins load times. I cleared the Windows TEMP files again, no change to the start times. I also have done several local file validations, no errors were found. RESULTS: ---------- Removed: WWII Asset, SA342 Aircraft, AJS37 Aircraft, F14 Aircraft (purchased this mod), AV8BNA Aircraft Load times changed from 1:40 without them to 3:18 when I added them back in... very interesting. I've attached the dcs.log files without & with them. The 1:40 is still much longer than I saw prior to loading 2.7.0. Startup was less than 1 minute on average to the main DCS screen. These are the errors I copied out of the dcs.log file so I knew where to put them back lol. ===== 2021-05-13 18:26:10.939 INFO SECURITYCONTROL: Loaded mods/tech/wwii units/dcs_module.pak.crypt 2021-05-13 18:27:08.410 ERROR WEAPONSBASE: invalid cx data <weapons.missiles.MBDA_Mistral><./CoreMods/aircraft/SA342/SA342_Weapons.lua> 2021-05-13 19:44:39.042 INFO Scripting: OBSOLETE mount_vfs_sound_path() used in ./CoreMods/aircraft/AJS37/entry.lua 2021-05-13 19:45:45.291 INFO EDCORE: Loaded D:/Program Files (x86)/Steam/steamapps/common/DCSWorld/CoreMods/aircraft/AV8BNA/bin/AV8B_AI.dll 2021-05-13 19:56:26.215 INFO Scripting: OBSOLETE mount_vfs_sound_path() used in ./Mods/aircraft/F14/entry.lua I also found 1 item in the dcs.log file that took time to load, I could not locate on my computer: ===== 2021-05-13 20:14:50.463 INFO SOUND: Added sound path: ./Mods/aircraft/FA-18C/Sounds And this one I could not make sense of: ===== 2021-05-13 20:15:41.721 INFO UIBASERENDERER: Cannot load font [D:\Program Files (x86)\Steam\steamapps\common\DCSWorld\dxgui\skins\fonts\]! dcs_removed.log dcs_with.log

Hi Flappie, I'm adding this post as I'm seeing extremely longer load times and closing times since upgraded to 2.7 Open Beta. Here are the tests I did yesterday and this morning. This was timed yesterday: From a fresh reboot = 2:54 seconds from starting DCS to the main menu After loading it once = 2:03 seconds to main menu This morning I did the same test: From a fresh reboot = 4:08 seconds to main menu After loading it once = 2:03 seconds to main menu Here are the numbers starting the game and loading a mission, then exiting: From a fresh reboot = 2:00 seconds to main menu Load a mission = :43 Select "Fly" = 1:18 Select which slot = :36 From the main menu after exiting the mission.. I added the dcs.log file again... that is the 3rd file Time back to the windows desktop = 2:06 Time to get "green" start to being another session = :36 So its 2:42 to exit from the main menu back to the desktop. Note, when exiting from the main menu, the screen goes black for that 2:06 time. All these times are significantly longer than previous version, which I would get to the main screen or back to windows in less than 1 minute. I have looked at the log files, unfortunate I'm not knowledgeable to really understand them... I just see a lot of errors. I have done local files validation, no errors were found. Yesterday I cleared out all my my windows temp files, It resolved the issue for a short time, unfortunately its now back to the same problem. When I cleared out the temp files yesterday From a fresh reboot = :53 seconds from starting DCS to the main menu Exiting was within a few seconds... back to normal As you see from the times this morning, the problem is back. Let me know if there is anything else I can provide to assist with this issue. I'm guessing others are having similar problems. Spaz dcs.log dcs.log.old dcs.log

I made some changes to my mission, specifically the size of the zones for the bombing targets. I thought possibly because they are over-lapping it may be causing the issue. I reviewed the Iron Bombing Range mission and see how they implemented the zones, so followed with the same implementation. Unfortunately it did not resolve the issue. I'm attaching my updated mission and the track file so you can see exactly what is happening. Spaz NM P51 Cardonville Practice.miz 210223_Spitz_Cordville_Bomb00.trk rangescript.lua

I've attached the .miz file to my previous post. Appreciate looking into this. Let me know if you have any questions or need additional information. Some times the reporting works, other times nothing. I'm just learning lua and scripting so my knowledge and experience at this point is limited. Thanks! Dave

Further testing of the rangescript.lua I sometimes get this error.. see the attached file. It appears to be related when at above min bombing altitude to launch bombs/rockets and I enter into zone. The message appears twice, which seems to coincide with enter zone and exit zone. I have set range.bombingMinAlt = 1800 I'm also finding the following issue: 1. strafing zone maxAlt = 1500, the in-zone messages are being displayed well above that altitude.. 3-4k Spaz NM P51 Cardonville Practice.miz

I have updated with the latest rangescript.lua, still seeing the same issue. Is anyone else experiencing the same? I'm no expert at with lua, I'll do my best to continue investigating. I lowered the min altitude and that appears to have gotten it functioning. Further testing has resulted in intermittent reporting of the accuracy. Will continue to test and investigate. 2/20: Lots of testing and have not been able to reproduce and problems, likely just my lack of understanding how things work. It is part of my standard tools when flying DCS, greatly appreciate the effort to create and maintain this capability for the DCS crews!

Thanks!, I did read it but didn't sink in until now. I'll update the mission and see if it works.

Hi, I've been using the Iron Bombing Range mission that utilizes the rangescript.lua, just realized this morning the bombing accuracy in meters is no longer being reported. I went back and did a fresh start with the original file from sidekick65 from the DCS User Files download, still no accuracy information being reported. Is anyone else seeing this?