Bullant

Sign me up, looking forward to a quality Hornet campaign.

There's a typo in quickstart.lua (note the extra N) file = 'NNevada FA-18C Ready on the Ramp.miz', Which means that the ready on the ramp quickstart mission does not show under instant action.

And to save you the trouble of having to create the entire file, here it is with all of the current modules. Note you will obviously need to modify the true/false flags according to what you own. pluginsEnabled = { ["A-10A by Eagle Dynamics"] = true, ["A-10C Warthog by Eagle Dynamics"] = true, ["AJS37 Viggen by Heatblur Simulations"] = true, ["AV-8B N/A by RAZBAM Sims"] = true, ["Bf 109 K-4 by Eagle Dynamics"] = false, ["C-101 Aviojet"] = false, ["Christen Eagle II by Magnitude 3 LLC"] = false, ["F-5E by Belsimtek"] = true, ["F-14B by Heatblur Simulations"] = true, ["F-15C"] = true, ["F-86F Sabre by Belsimtek"] = true, ["F/A-18C"] = true, ["Flaming Cliffs by Eagle Dynamics"] = true, ["FW-190D9 Dora by Eagle Dynamics"] = true, ["Ka-50 Black Shark by Eagle Dynamics"] = true, ["L-39C"] = false, ["M-2000C by RAZBAM Sims"] = false, ["Mi-8MTV2 Hip by Belsimtek"] = false, ["MiG-15bis by Belsimtek"] = false, ["MiG-19P by RAZBAM"] = false, ["MiG-21Bis by Magnitude 3 LLC"] = false, ["MiG-29 Fulcrum by Eagle Dynamics"] = false, ["P-51D Mustang by Eagle Dynamics"] = true, ["SA342 Gazelle by Polychop-Simulations"] = false, ["Spitfire LF Mk. IX by Eagle Dynamics"] = true, ["Su-25A by Eagle Dynamics"] = true, ["Su-27 Flanker by Eagle Dynamics"] = true, ["Su-33 Flanker by Eagle Dynamics"] = true, ["UH-1H Huey by Belsimtek"] = true, ["Yak-52 by Eagle Dynamics"] = false } -- end of pluginsEnabled Thanks Pudu for the instructions on this.

32Gb system memory here, no page file (SSDs). Crashing at 22Gb memory usage. Swap file is not the issue.

Posted this in the other ctd thread, putting it here in case it helps the devs: OK done a fair bit of testing, hope this helps the devs. I have 32Gb of ram, MSI afterburner shows 10Gb in use with just background crap (outlook, chrome etc). Launching the alert 5 mission this quickly climbs to 22Gb and CTD. If I cut back some of my graphic settings it starts at 20Gb, I can look around for a bit but it soon climbs to 22Gb and crashes. In the hornet, on the carrier in PG, starts at 16Gb never gets above 18Gb. If I put the DCS settings to the Low preset, Alert 5 PG starts at 16Gb and climbs to around 20 and seems to keep working. If I close outlook and chrome, my base mem usage drops to 6Gb. Alert 5 PG then starts at 16Gb (with my high settings) and climbs to around 20 after a couple of minutes. Seems stable for a while but then crashes. This is definitely a memory issue, and obviously made worse by the higher memory usage of PG & the Tomcat, the question is why is it crashing when memory usage hits 22Gb and I still have 10Gb of free memory? I tried hitting 22Gb in the Hornet and couldn't really come close ... Forgot to say, Tomcat on Caucus at high settings started around 16Gb and climbed to around 20Gb ... not sure about long term stability, need time to actually fly a real mission.

OK done a fair bit of testing, hope this helps the devs. I have 32Gb of ram, MSI afterburner shows 10Gb in use with just background crap (outlook, chrome etc). Launching the alert 5 mission this quickly climbs to 22Gb and CTD. If I cut back some of my graphic settings it starts at 20Gb, I can look around for a bit but it soon climbs to 22Gb and crashes. In the hornet, on the carrier in PG, starts at 16Gb never gets above 18Gb. If I put the DCS settings to the Low preset, Alert 5 PG starts at 16Gb and climbs to around 20 and seems to keep working. If I close outlook and chrome, my base mem usage drops to 6Gb. Alert 5 PG then starts at 16Gb (with my high settings) and climbs to around 20 after a couple of minutes. Seems stable for a while but then crashes. This is definitely a memory issue, and obviously made worse by the higher memory usage of PG & the Tomcat, the question is why is it crashing when memory usage hits 22Gb and I still have 10Gb of free memory? I tried hitting 22Gb in the Hornet and couldn't really come close ... Forgot to say, Tomcat on Caucus at high settings started around 16Gb and climbed to around 20Gb ... not sure about long term stability, need time to actually fly a real mission.

Had to google DEP, but after checking I can see it is enabled for "essential Windows progams and services only" so don't think that's my problem. There are definitely memory errors in my log when it crashes, but I am only using at max 20 of my 32 gig of memory (you can clearly see where the crash happens on the graph attached)

Not a single mod.

Same here, and it's not just the F14. Tried a couple of modules and they all do it now.

More info, any instant action mission in Persian Gulf or Nevada results in instant or near instant CTD. Was able to fly around in Caucus and Normandy for 10 minutes each without a problem. Also as you can see I have heaps of memory, a juicy graphics card etc. Never had a problem with Nevada or Persian Gulf in any other module.

Here's my dcs.log for the Persian Gulf Alert 5 mission. I hadn't even hit fly yet, was just looking around and it CTD. dcs.zip

lol this is a feature, and it is fantastic.

I thought I was being petty, but I felt the same way. Switched back to the F18 wallpaper ... It's a minor thing, but there are so many good, hires images of the cat out there.

It should do, the post above says the fix will put Jester in the center of your user interface viewport.

Cobra, this is not just a VR issue. I have 3 x 1920x1200 screens and trackIR and running on the highest settings for everything. I can't make out the text on a lot of panels even if I move my face right up against the screen. I don't have problems reading panel text in any other module.

Brilliant, thanks for the fast response on what must be a super busy day :)

I have an exotic but probably not unusual monitor configuration. 3 x 1920x1200p monitors as my main display 2 x 1024x768 monitors sitting behind MFDs I have them arranged in windows so that the MFD monitors sit to the right of the 3 main monitors. This means I have a resolution of 7808x1200 selected in DCS settings. My monitor config file is attached. Note that I have been flying using just the center monitor for the sim due to the HUD/MFD issue in the hornet, in this configuration the Jester wheel is only half visible, with the rest off the screen. Using all 3 monitors, the Jester wheel is off to the right, but at least visible. It is apparent that the Jester wheel is being positioned in the middle of the overall resolution, rather than in the middle of the defined "Center" viewport. This make Jester unusable in single screen and virtually unusable in 3 screen setup (because I can't look at the selection with trackIR to use it). Now I can work around this for the moment by changing my monitor config to remove the 2 MFD monitors, but I really wanted to put the F14 displays on them ... 5_monitors-FA18C.lua

I almost didn't pre-order because of this. I found the text illegible in a lot of the pre-release videos and even in the manual, but figured it would be better in the flesh. Nope :( I get that the aircraft is worn, but the devs also have to understand that IRL the pilots KNOW what each button does from muscle memory and don't have to read the labels. Us armchair pilots trying to learn a brand new bird don't have that luxury. So please, be weathered by all means, but please keep the panel text readable. Please.

I've only tried two missions (have to work :() Caucus takeoff mission is fine, but Persian Gulf alert 5 mission crashes to desktop as soon as I hit fly. Tried twice with exact same result.

mmm 1500Z = 0300 local tomorrow. Bugger ...

Don't even need that, 3 minutes with a little file and the inbuilt detent can be turned into a push through that works perfectly once you set up the throttle curves correctly.

Do you not find that the inbuilt AB detent works? I don't think I've ever engaged AB unintentionally since I did the mod to sand the edge of the gate down a bit so I can push through it.

Also ... best launch trailer. EVER!

16 hours into the 13th here ... just saying. My "check for updates" button is almost worn out ;)

Bugger! Here I was saving my pennies hoping I'd be able to afford one of these in the next couple of years to go in my full pit. Back to the drawing board ...