H60MTI

Infantry is pretty soft *evil grin*

You can tell it detonates a little above the target but not enough to make it have a bigger effect. I'd just stick with a normal fuse. That's just my opinion. If you could adjust the height of the detonation, especially with all 8 GBU-32's, then you could do some damage.

Has anyone used this fuse yet? Seems like it's an airburst nose fuse. Just curious if anyone has used it and know if it's worth using on enemy planes sitting on the tarmac. I also noticed there's no forum for just the weapons...Don't know if that's something the moderators could look into...

It's probably just me but, how do I do anything in the F-15EX? Seems like my mouse doesn't do anything, hell I can't even see the mouse arrow. HUD doesn't turn on, can't click on any of the MFD functions. I know it's based on FC3, but I literally can't do anything besides just fly. Is there a read-me I missed somewhere?

Also, did the Tanukji44 minigun mod go away? Trying to get the armed Blackhawk back but need that minigun mods first. Does anyone know where it went to or have it by chance?

This been working with the latest version of DCS OpenBeta? I know I uninstalled it awhile ago but would like to get it back.

I'm thinking that's all it was. I put all my sticks, 64GB worth, and it's running fine now. Was playing Ghost Recon: Breakpoint a bit earlier and now I'm in DCS with no issues. Seems like a stick just needed to be reseated for reason. Don't know why after a couple of years in it. Beats me but she's running like she usually does.

Hey everyone. Just downloaded this mod a bit ago. I have the TM HOTAS Warthog as I'm sure many of y'all do. How did you do your bindings for the eng/throttle? That two step throttle with Off/IGN/Run is throwing me for some reason and can't get it right. Ideally, I would have a momentary switch for start. Another momentary switch for IGN position. Then once spooling, advance the throttle for idle/run. Like I said, for some reason, that's throwing my brain for a loop and can't quite get it work how I want.

Update...Was running on 2 sticks of RAM, 32GB total, since last post. I've got all 4 sticks back in to try and narrow down the bad stick and or bad slots in my motherboard. So far so good, some how. Was running Ghost Recon: Breakpoint for a bit and I'm swapping over to DCS as we speak. We'll see what happens.

Got it! More smoke/marking type of rocket then some actual Willy Pete....Definitely need some Willy Pete in the game...And napalm. Great fits for the F-4E.

I'm seeing for rockets 3 different version. Mk1 HE, Mk5 HEAT, and the M156 Wht Phos. Probably a dumb question but is that more of a smoke marker rocket or is that some full-on Willy Pete??

I'll definitely give it a shot. I do have XMP enable. With a Ryzen CPU of course I have XMP enabled Lol I wasn't really able to get into BIOS before cause of the looping BSOD's.

So, it has to be a bad RAM stick or a bad channel. I tried each stick separately and computer booted just fine. At the moment I'm in DCS and it's kicking with 2 sticks in dual channel mode. When I get some more free time, I'll try all 4 sticks again and see what happens. PITA!!!

I'm back-ish. I'm thinking a bad RAM stick. Right now I'm running on one RAM stick, so 16GB of DDR4 GSkill Trident Z RGB. Good stuff. I typically run 4 sticks of said RAM. Before I went offline I was having constant/looping BSOD's. So, I'm running one stick at a time and seeing if I find a bad stick that won't boot Windows.

Well, we're past DCS and games crashing. Definitely a rig issue and I don't know what. I'm getting looping BSOD with restarts or shut downs. Not even time to troubleshoot cause it BSOD's. I think I'll tear the rig apart and rebuild it. This is ridiculous. Thanks for the help guys, I do appreciate it. Cross your fingers and pray.

And crash....Oh my God this is annoying. DxDiag.txt

WTF? I can't curse anymore?! That sucks.... Thanks ED... We're back. Updated DCS. Ran rebuild and cleanup. Ran dism and scannow prompts. Shut down and reseated my RAM. Let's see what happens...

Yeah, that's all stuff that I've run today. DCS obviously. I was running Cinebench and FurMark earlier to try and see if my rig was stable. Both of those are stress testers. FurMark is a graphics stress test and Cinebench is a CPU stress test. Ghost Recon: Breakpoint is another game that I play. So, if I'm seeing hardware and not handling memory properly, I wonder if a RAM stick isn't seated right or has going bad.... Just ran those 2 prompts. I'm going to shut down actually and reseat all my RAM for <profanity>s and giggles.

Here is the DxDiag results. Just tried DCS again and still crashed. Just updated it as well with the version that just dropped. I also just removed all my mods from Saved Games and stashed them on one of my other hard drives not associated with the game. About to try that. I've noticed that sometimes DCS just freezes and doesn't show the file that causes the crash in the log. Just stops responding and can't produce a log file. DxDiag.txt

I went in and cleared most of those files mentioned above. There were some that I couldn't because they were being used at the time and couldn't erase them. Didn't help, at least for Ghost Recon Breakpoint. It still crashes. I'm probably going to have to break my rig down and see if anything is jacked up.

Hell, it could have been a cement plant for all I know but it was definitely a USMC ran camp/FOB that had UH-1's and AH-1's stationed there.

No, not there. This place didn't have an actual runway.

I updated my driver this morning. Had a day off work cause my kids school is closed for voting. Why they use elementary schools for voting locations is beyond me. I actually went to play Ghost Recon Breakpoint and that crashes as well. Weird. Funny thing is, I ran FurMark and Cinebench R23 at the same time as everything was stable. I don't understand it. Those numbers are after a 10 minute run of FurMark and Cinebench running at the same time on separate monitors. You would think stressing the system like that would cause something to crash. I'll try dumping those folders and see what happens.

I am on 565.90. They are currently on 566.03. I'll have to install that later and hope for the best.

It could be the Nvidia driver. That is having issues with Corsair iCue. I had to roll back iCue to work properly. I'll do some digging later. Thanks so far. I'll see what I can come up with.