Jump to content

Recommended Posts

Posted

Can't enjoy till its changed,dcs p51 is on shelf.

Intel i5 3.2 ghz

8 GB crucial ram

gtx 660 superclocked 2gb

500watt corsair psu

win7 64bit

extreme pro

track ir5

Turtle beach x12

  • 2 weeks later...
  • 2 months later...
Posted
http://forums.eagle.ru/showthread.php?t=95947

 

Echo doesn't need me to speak for him but we've been here before...! Echo said in above thread...

 

 

 

No dis-respect intended at all Al Capwn, but these 50cal effects are over exaggerated at the moment by too great a factor.

 

 

Solid hits right there mate!!

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

  • 9 months later...
Posted

P-51 FPS gun fire

 

Not sure if its been mentioned, When firing the P-51 guns it killes the FPS. Is this something that is being fixed?

[sIGPIC][/sIGPIC]

Posted (edited)

Does anyone know which file I need to delete to get rid of the P-51 gun smoke? It's probably the cause of the fps issue and most people experience it, same with say the CBU-87/105. Hopefully the smoke file isn't shared with the other aircraft or it's a variable.

 

Edit: It may also be the tracers, or both.

Edited by SyntaxError

RimOnBlue.png

F/A-18C - A-10C - FC3 - L-39C/ZA - Ka-50 - UH-1H - Mi-8MTV2 - F-86F - Spitfire - P-51D - P-47D - BF-109K - CA

Posted

You guys could try editing tracer_bullet_red.lods file found in .../Bazar/World/Shapes folder

 

values are like this

lods = {

{"tracer_bullet_red.edm",600.000000};

{"tracer_bullet_red-LOD.edm",2000.000000};

{"tracer_bullet_red-LOD2.edm",1000000.000000};

};

 

I think the last one is way excessive... who would see tracers 1000km away? Also, I don't understand why 6 decimals in these lods files?

 

Try changing it to

lods = {

{"tracer_bullet_red.edm",600};

{"tracer_bullet_red-LOD.edm",2000};

{"tracer_bullet_red-LOD2.edm",10000};

};

 

I wonder if it will improve FPS when firing guns

PC specs:

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi | AMD Ryzen 7 9800X3D + LC 360 AIO | MSI RTX 5090 LC 360 AIO | 55" Samsung Odyssey Gen 2 | 64GB PC5-48000 DDR5 | 1TB M2 SSD for OS | 2TB M2 SSD for DCS | NZXT C1000 Gold ATX 3.1 1000W | TM Cougar Throttle, Floor Mounted MongoosT-50 Grip on TM Cougar board, MFG Crosswind, Track IR

  • 2 weeks later...
Posted (edited)
You guys could try editing tracer_bullet_red.lods file found in .../Bazar/World/Shapes folder

 

values are like this

 

 

I think the last one is way excessive... who would see tracers 1000km away? Also, I don't understand why 6 decimals in these lods files?

 

Try changing it to

 

 

I wonder if it will improve FPS when firing guns

 

Hi, this worked surprisingly well for me and most of my mates (including Injerin). Great fix! Thanks! :thumbup:

 

I did a few stress tests with 40, 80, and 160 planes dogfighting. 160 seemed to be a few too many for my little video card to handle, but 80 ran smoothly with gunfire.

 

We did have one (slightly) unrelated problem though. (I might post this in another thread if it is too off topic)

 

Gunfire no longer causes any FPS drop. I can watch 40 planes shooting tracers with no dip. However, Fire/smoke effects cause a massive FPS hit. (Basically I can look at 5 aircraft firing tracers with 60 FPS, but if I look down at five burning wrecks, my FPS drops to 1)

 

Is there any way to edit an FPS friendly smoke effect?

 

I may try editing the number of particles that spawn for smoke and see if that helps, because distant smoke effect seems to have little impact compared to closer burning wrecks, but I'm rather new at editing files like this, so I'm hoping someone smarter and more experienced might be able to chime in with some ideas :smartass:

Edited by NakedSquirrel

Modules: A10C, AV8, M2000C, AJS-37, MiG-21, MiG-19, MiG-15, F86F, F5E, F14A/B, F16C, F18C, P51, P47, Spitfire IX, Bf109K, Fw190-D, UH-1, Ka-50, SA342 Gazelle, Mi8, Christian Eagle II, CA, FC3

  • 2 weeks later...
Posted (edited)

Still no word on the FPS issue?

 

We have monster PCs and we are seeing ridiculous FPS hits every time the guns are fired. No updates on this?

 

We also saw something incredible that will be in my next sh*ts and giggles. When one of our P-51D pilots was flying and guns were being fired, his entire screen froze due to the FPS drop and he crashed. When I looked to see his impact point, it looked like a nuke went off. The explosion was about 10000X bigger than it should have.

 

Really weird... but really cool, please don't change that.

Edited by ralfidude
Posted

I have requested this since 1.2.3 but no one joined my voice.. It's a shame I can't properly fly and FIGHT in this aircraft just because ED cannot finish their product. Either remove the smoke effect ED, or make it like 1.2.1 (laser tracers).... This is bellshit

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

All three of my friends experience this, and i have a sound card. It's not the sound...

 

We got the P-51D on sale and we all can't play it because of how horrible it is when you press the trigger. One dude froze up so bad he crashed, while the other who was hosting froze so bad it crashed the game for everyone.

 

I tried running it off my server too and same crap.

 

Something horrible is going on.

Posted
One dude froze up so bad he crashed, while the other who was hosting froze so bad it crashed the game for everyone.

 

Does the same happen offline? If not, some of you may have too slow network link. Lots of bullets -> lots of network packets -> network congestion.

Wir sehen uns in Walhalla.

Posted

Strange. I'm not getting that bad of an FPS hit. I average about 53 without guns firing and 48 with. I attached my dxdiag so maybe that will help. It says I have a GTX 780 now, but back when I was using a GTX 570 they still weren't as bad as some reports. Also attached is a screenshot of my settings.

DxDiag.txt

options.png.3c4f8945e2ba365e40dddc0bbe6f086c.png

Posted

It's been horrible for months. I made a post about it way back in July, and it was a problem long before I posted about it. There have been several patches and nothing has been done about it. All of my friends with P-51 have the same problem too. If I fire in very short bursts, it's tolerable. If I hold down the trigger for a few seconds I can have my fps drop into the teens easily.

 

Core i5 760 at 3.66 ghz. WD Black, 12 gigs ram, Radeon 7950 on a single 1920x1200 screen is what I'm running.

Posted

Guns don't cause FPS drop. People cause FPS drop.

 

I'm really, really sorry. My eyes fell on the thread title and...

 

;)

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted

ED is underfunded and overworked. You bastards need to buy whatever they come out with next. No questions asked.

I'd rather have a bottle in front of me than a frontal lobotomy and I've had both.

 

[sIGPIC][/sIGPIC]

Posted

No tflash.

 

If you read the entire thread you would see that a lot of these people are running good rigs.

 

I know that myself and Linebacker are both running very fine PCs and still experience this issue.

 

CPU is a new gen i7 6core (i know cores dont do sh*t in this sim) OC'd to 4.8GHz (this matters) and liquid cooling.

 

ASUS motherboard with 16GB of RAM at 2400

 

GTX 690

 

game running on an SSD...

 

Low specs are not the issue here mate.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...