hawk2495

Ditto on all of the above. 9900K @ 4.8Ghz, 64GB 3200 DDR4, and a 2080. Now, when I run it flatscreen I show red GPU bound which is what I would expect with a 2080 in my system. I need to do some more checking on my actual CPU usage though. Of course, every time I get settled in and start doing something it's time for the family to "need" something. lol

Now I'm not sure if anyone else has had this happen. I'm working on building training mission to kinda get back into flying and using AI to test my triggers and such. In testing, I've noted that any Apache that takes taxiways Bravo, Hotel, Delta, will flip forward and explode upon attempting to transition to Delta from Hotel. I went ahead and tested this with Hind, and Black Shark and they transitioned fine. I thought maybe it was a tail dragger thing and tested with a Jug and Spit. Worked fine. So it appears to just be the Apache affected at this point. It was odd and I figured I should bring it up. Depending on where you end up parking your birds, it makes having more than a 2-ship pointless as any other birds seem to just go boom.

Hell, there are entire panels that have nothing at all. I had to dig through the .luas to create my own for the APU-Engine start panel.

Woohoo! This chopper just has too damn many break levers... lol

Thanks Wags for reminding me that I haven't yet installed a word processing program on my computer since my last reformat... lol

Is your wheel brake on? I had an issue with that yesterday.

The big ones for me are all of the controls on the APU-Engine start panel. All of those are missing. I'm going to look through the .luas and see if I can make my own though.

Yep. Figured it out about a minute after I hit post. lol

Please disregard. I found the issue. If a mod could delete this for me please I'd be grateful

Awesome! Thank you. Works beautifully! I really wish ED and partners would go through and do this with all the switches so we wouldn't have to. Oh well. It is such a small thing to worry about.

Of course, that makes sense. Thanks. I'm using a normal Single Pole/Single Throw for the LB switch and an SP/Double Throw for the AP switch. Both are wired to a GPWiz 40 joystick encoder board as normal dx inputs. The only one that is really annoying is the AP switch. If all else fails I'll just bind them to some buttons I have on my switch box instead of switches if I can't find a command combo that will work.

Okay, not totally sure the title is going to help with this. So, I've been creating toggle commands in my input.luas using this awesome tutorial https://forums.eagle.ru/forum/english/dcs-world-topics/input-and-output/87627-how-to-set-up-toggle-switches-a-tutorial It has worked beautifully on almost every module I have. I have, however, noticed a couple of switches that only function properly when the plane is cold and dark. Both the Launch Bar switch in the Hornet, and the Pitch A/P Switch in the Viper. I'm wondering if anyone else has seen something similar. When cold and dark the LB Switch works as advertised. I put the switch up, it goes up. Flip it down, down. When the plane is running, I have to toggle the switch like I would if it were on the standard binding. On the Viper's A/P Pitch I have all 3 positions mapped for a on-off-on 3 pos switch. When cold, it cycles perfectly. When hot, I can set the Alt hold on, and that's it. The other positions stop responding. So, is it just my setup or have others doing this had similar issues?

Please delete.

Well since Snoopy works with Hogs on a daily basis. I'd say he might be a good person to ask. AFAIR he's been at it for quite a few years too..........

Looking forward to it Baltic!!

I don't know. The documentation seemed pretty clear. The GPS is to correct for INS drift. And it's only accurate to within 50 ft. Which, from my testing, is about how far off it is when it misses. So, from what I've seen and read. It seems fairly correct. It's only job is to get the weapon on target in a manner that the pilot would only have to do a short search with the D/L to acquire the target. Now the SLAM-ER, on the other hand, can be used in fire and forget situations due to its ATA (Auto Target Acquisition) system. Which the SLAM doesn't have. I'm open to correction on that part.

Let's look at it this way. Internal testing is usually on machines that are very similar in spec and software environment. So what works internally isn't necessarily going to work on Joe Schmoe's computer that is setup differently. Kinda the reason for the Opne Beta. Get the biggest sample size you can to test any changes. My performance is on par with the past few releases. Though I do have an occasional weird FPS drop, but not game breaking.

That is one buggy piss. Or is it a pissy bug? What was I saying?

I've got a 9900k @ 4.7 a 2080 at stock and 32 GB 3200 Mhz RAM

Is everyone using Vsync? In my case I turned it off and managed to at least get a gradual frame drop. From 70 looking forward on the cold start to about 45 looking aft. Not too bad. With high shadows and 2x MSAA in 4k

Then I decided to turn of VSync. The frame drops became far far less severe.

Here's what I've been seeing on a clean deck. There's just about a 5 degree zone where I get a drop looking aft toward the LSO station. For me, the Island is just fine. This is again 4k with everything on high minus MSAA and SSAA.

"2. Go fornicate yourself." "Roger." SPLASH!

The missions were folded into the F/A-18 list. They're toward the bottom. So far only normal missions. No instant action.

I was doing a test on a clean deck. My hit was when I looked over toward the LSO station. Maybe the displays are causing a hit? They appear to be active at all times..