Flapjacks

It ended up being the GPU. Just got my PC back today and FPS is 100+. I appreciate all the help folks!

I use to see that happen as well with other JDAMS, flying past the target a little then angling back to hit them.

Sorry for yet another question but are these fairly easy to swap out? I was pretty hesitant to try to do the gpu myself but tried anyways.

I'm not sure what is considered cheap pricewise. Just browsing I seen two: CORSAIR CX750M 80 PLUS Bronze Semi-Modular Low-Noise ATX 750 Watt Power Supply - NA - Black and EVGA SuperNOVA 750 GT, 80 Plus Gold 750W, Fully Modular, Auto Eco Mode with FDB Fan, 7 Year Warranty, Includes Power ON Self Tester, Compact 150mm Size, Power Supply 220-GT-0750-Y1

Alright, I'll look into getting a new PSU. Y'all think I'd be safe getting a 750w then? Any brand recommendation or to stay away from?

I didn't see anything about recommend power on the box but yes I was using an adapter that came with it. Guess I'll have to buy a new PSU.

the new GPU is from Asus. The only connector was the one from the PSU and I might have heard a very faint beeping. I'll have to re-install it later on and have a listen to make sure.

Apex AL-D500EXP Also says Model no: SL-8500BTX

Old GPU is a RTX 2060 and new one is RTX 4070 Super. Board is ASRock H310CM-HDV. Not sure about the rest.

Hey, so I tried to install a new GPU earlier (my first time trying this) but never got a signal to the monitor, no picture at all. I opened it back up again to make sure all the connections were good and they were. Cable was plugged into the GPU slot (not the motherboard), I saw a red light on the GPU so it was getting power. I took it out and put the old one back in and it works just as it did before. Any suggestions on what I can do?

So I noticed that some of the targets I usually have had no problem bombing with GBU-54's now aren't being killed as consistently. I saw this line in the changelog for yesterday's patch. Weapons. Corrected aiming data for GBU-10, KAB-1500-LG-Pr, KAB-1500LG, GBU-24, KAB-500L, GBU-54, GBU-12. I did some testing and with the same coordinates entered for each type of bomb, the GBU-38's take out the targets no problem, but the GBU-54's seem to fall a little short only damaging the targets. *Edit* just to be clear, I'm using the same exact coordinates that are set in the mission editor for both types of bomb. GBU-54.trk GBU-38.trk

This bug wasn't fixed with today's patch. Please look into this Razbam. Stations L1 and R1 aren't releasing JDAMS properly. They lose speed and fall way short of their targets when dropped from IN RANGE distances. I've found that if I'm at roughly 35k ft and above 400 CAS that they seem to work properly or if I get within IN ZONE distances and slow to roughly 440 CAS.

Gpu is running hot. Gonna see about replacing it and see if that fixes it.

Still no improvement, I appreciate the help. Think I'm stuck with this.

I made those changes but no luck.

Game bar is off HAGS is on.

@silverdevil Global settings DCS settings

Not sure how to copy the 3D settings to show in this post.

I've tried them all but nothing helps. I have anti-aliasing off for now.

Nothing I'm aware of. Another patch is dropping soon though I believe.

So I've had extremely bad framerates for months now and I've been chalking it up to the 2.9 patch, but figured I'd ask to see if possibly it was on my end. My fps is at like 7-10 fps on the ground and low 20's in air. It's the same on both Openbeta, MT Openbeta and Stable (which I have on two difference drives) as well as multiplayer and single player. I don't have any mods anymore I don't think, I've turned off tacview, graphic settings are low, vsync is off as well. Drivers are up to date. I've gone through all kinds of tips and tricks that I've read on a couple of the 2.9 problems posts (power management settings, Nividia control panel settings, etc), I've run slow repairs, deleted fxo and metashader folders. dxdiag and device manager says no problems found with my gpu. I know I need more ram btw (16 gb) but it never ran this bad before. Is there at least any way to check if the problem is on my end or not? DxDiag.txt dcs.log

Just wanted to update that this is still a problem. Hopefully it gets fixed with the next patch. JDAMS from stations L1 and R1 lose energy and end up falling short of their targets. Tested with every JDAM I believe and all have done it. It doesn't happen every time, but happens quite often.

Not sure what to use then to view/change to decimal minutes.

It's saved as a .tw file. I can open it with wordpad but the coordinates don't match up to the ones from the same file loaded into the app.

Hey, is there a way to manually change coordinates to a saved file? Or a way to change the coordinates of waypoints loaded into the app?