mboddicker

I was trying to implement SWAPR in a new mission and ran into the following error: Mission script error: [string "Scripts/Moose/Wrapper/Airbase.lua"]:515: attempt to index local 'DCSAirbase' (a nil value) Since this was coming from Moose, I loaded the sample mission that comes in the SWAPR_1_3 download. After testing it without any mods SWAPR worked correctly. I updated Moose within the test mission to the latest version in the Release branch. This caused the same error as I was seeing in my mission. After more troubleshooting, I found a fix. Needed to modify lines 320, 322 and 324 in the SWAPR_1_3.lua, changing "GetClosestAirbase(Airbase.Category.AIRDROME)" to "GetClosestAirbase2(Airbase.Category.AIRDROME)". This change allowed SWAPR to work again for me. Something must have changed in the latest updates to Moose.

I have the same problem in VR. It takes forever but I eventually could arm all three switches. I later tried it again using TrackIR and had the exact same issues so it affects more then just VR.

The fix today seams to have resolved my issues. Thanks ED!!!

I'm not saying its unplayable for everyone, I am saying it is completely unplayable for me. None of the click spots align at 4k resolutions for me. From the main menu I have to spend several minutes finding a click spot which appears to be in the upper left say about 1920 x 1080 pixels of my 3840 x 2160 resolution. The click spots are significantly smaller as well so very difficult to find and select something. So with the F-18 background image, the module icons displayed at the bottom highlight when my mouse is on the horizontal plane with the middle of the F-18 fuselage from behind the jet exhaust to about the middle of the right wing. The "Exit" button highlights when hovering just above the plane number on the right wing. Getting to and adjusting settings is extremely difficult. I've also tried the mission editor and everything is off there as well. What I haven't tried is loading an actual mission to see if the click spots are also off in cockpit. I haven't bothered yet because it would just be an exercise in frustration. I stand by what I stated, it is unplayable right now for me and it sounds like for others as well. ****Update**** Ok, I decided to do a couple of test to give additional information. First off, I did go ahead and test click-spots in cockpit and found that they do work as they should. If however you press ESC to access the menu to adjust controls, view the briefing etc., the menu that pops up will have the clickspot offset issue. Next, i renamed my options.lua file so it would build a new one on startup. First I only changed the resolution option to set my 4k resolution. After the restart, clickspots were good so next I enabled the Scale GUI option (using Win10 175% scaling option). After a restart, the click spot offset issue comes back. I tried with Full Screen both on and off and no difference. Hopefully somebody can figure this one out soon.

I'm running 398.11 and have the same issues. This is not a driver issue. This latest version of DCS is unplayable using a resolution of 3840 x 2160.

I want to thank you for this, it helped me a lot when trying to manage my throttle!!!

Yep, was stationed out of Yokosuka and lived on the boat full time. I always envied the air wing guys cause you got to move off the boat in port. If only I would have let the MEPS guy talk me into being an AT instead of DS, then I could have lived in cushy barracks when in port too. :lol: In Nov of 93' I flew into Narita and checked in to the Indy the night before getting underway for a deployment to the gulf. Were you able to avoid that cruise? Funny thing about the JP5, I've been out since 97' and a couple of years ago I was in San Diego for a conference. I was staying at a hotel just a couple of blocks from the USS Midway so I took a tour. The first thing I noticed was the smell of JP5 and it instantly brought back a bunch of memories. :smilewink: And water just doesn't taste the same without that JP5 flavor either.

Ryanj73, Good to see a fellow Indy vet on here. I was a DS3 on the USS Independence from 93' to 95'. I've even got a patch from your squadron somewhere around here.

Flamin Squirrel, Good program so far but I have some possible suggestions for you. 1. When opening the program, all measurement settings default to metric. On the app close event could you have the program save the users settings values to a xml config file? Then when opening up the app, set the default settings according to the saved config file. 2. Add the ability to save/load a mission. Would need to add a mission name and mission description field. 3. Whats interesting about your program is its ability to calculate fuel burn. It would be interesting to see a summary for the total estimated fuel burn for all phases of the mission, and to use that to estimate how much initial fuel should be loaded on the aircraft. I don't image the Air Force sends every plane up on every mission with a full load of fuel. 4. On the take-off tab, could you also show V1 and V2 to go along with Vr? 5. On the summary tab, output the entered data in a format that could be copied and pasted into DCS Mission Editor to be included in mission briefings. If you coded this in VB.NET and want some help, I do that by trade and would be happy to help.

Druid, I re-downloaded the mission and tried it again. I get the same fatal crash during the loading process where the bar gets to around 90-95% loaded. I'll wait and try the mission again after SP5 is release. I was able to load an ED mission prior to running your mission.

Druid, I tried to play your mission version 1.2, but unfortunately for me its causing a fatal crash while loading. This is the first user created mission that I've had a problem loading.

Sabre-SLA, good mission. It took me four times but I finally got a Qualified rating. The first two times I ran out of time as I was worried about the order I was doing everything. The third time I didn't worry about that and started everything up the way I always do, but I forgot to enable nose wheel steering and failed. By the fourth time I had everything started up correctly although I was concerned the EAC not being active was going to cause me to fail again. That didn't happen so all was good and I passed the mission. I'm looking forward to all your future training missions.