Rider1

Apologies to Eno for crapping in the thread... Sorry, man.

Shagrat, do me a favor. Boot up A10C. Ripple off 4 87s, and shoot off a 21 pack of rockets.. Then maybe for good measure shoot a full drum of ammo at a target. Please note your frame rates.. Now boot up World and do the exact same thing. Please note your frame rates. Report back here. :music_whistling: If you got guys with cutting edge computers running everything else they throw at it without out breaking a sweat and then drop one CBU in World and it brings the system to a crawl it's not the hardware. It is a coding/testing/QA issue that these bugs are making it into public releases...

So compare DCS to DCS.. Load up DCS A10C and go head and drop 87s and 97s, fire rockets, blow the crap out of everyhing and tell me what your frames do.. Not much drop if any right? ED nailed it with A10C. The game just runs like a dream.. ED, take a look at that. What the hell happened with World? Why were these effects changed and put out there in such a buggy state? Did not one single Dev or tester not look at the cbu slideshow and go Holy crap! That's not good at all.. Let's release it anyway. Look at this post: http://forums.eagle.ru/showthread.php?t=89845 June of last year was when people started having CBU and effects slideshows. ED it has been 9 months we have been waiting to for you to fix this.. And oh hell lets just dump on some frame crippling burning smoke into the whole mess too.. Seriously what were they thinking?

I'm happy it is working out for you guys. Thank you. I spent the last few weeks rage editing the crap out of any file that had the word smoke in the file name in a selfish effort to make my game fun again. Glad it worked out for the better. Here's hoping 124 will fix these performance issues.

Jeez TZeer Your before shots of the 38 FPS.. i am lucky to get 40 FPS consistently just flying a typical multilplayer mission under normal conditions :( My specs: Win7 64 | ATI 6850 w Cat 13 driverset | AMD 2.6 Phenom Quad Core | 8GB ram

You might try just playing the standalone A10C version until you get a new rig. It is much kinder on FPS and resources than World is right now. Your World serial number will work to activate it. DCS A10C Warthog 1.1.1.1 Final http://www.digitalcombatsimulator.com/en/downloads/previous_versions/dcs_a10c_warthog_english_1.1.1.1/

OK I think I got it. Could someone be so kind as to replace your JSmoke.cfg and JSmoke2.cfg with the ones I have attached? They go in here: C:\Program Files\Eagle Dynamics\DCS World\Config\Smoke Don't forget to back up your old ones first, right? :) Then please run the attached mission. Shoot the Russian tanker and the Sue. Have a look at the burning wrecks and see what your frame rates are doing and report back here with your findings. I get no FPS drop on my rig, well a maybe little because of the other effects going on, but the slide show is pretty much history.. Along with the smoke. Fingers crossed... Caveat: I have no idea if this affects any other smoke in the game, like marker rockets or burning ships... JSmoke.cfg JSmoke2.cfg shoot the tanker.miz

Thanks. Those were what I needed:thumbup:

Topic: I have found the files that control the smoke. Here is what I have so far. First, I am testing my findings on one vehicle. A static fuel truck. The one I am using is at the harbor, just North of Batumi, sitting 50 yards from the cruise ships docked there. I use this one because it is one of the objects that when burning, drops my frame rates to single digits. I am pretty sure that it is burning fuel that causes the drop. Go here: C:\Program Files\Eagle Dynamics\DCS World\Config\Smoke In here are two files: JSmoke.cfg JSmoke2.cfg. If you look in these files there are settings for burn time, age, particles.. example: [11]= { ["value"]=1000, ["name"]="maxParticles", ["range"]= { [1]=0, [2]=1, }, If you look down at all these values, you will see that they are pretty low but you will also see that a few have settings of 1000. Very odd because most of the other similar parameters are not really over 5. So I changed them to 1 and saw some improvement, the smoke is not as heavy, but still lagging my system. So I started changing all of the age and duration settings to 1. So now I have less smoke but the FPS drop only lasts 10 seconds or so. I am probably going to change everything in there that looks like it has to do with smoke life, and particle values to 0 right across the board. and see if that takes care of this problem completely. 1) I do not know if one or both of these files need to be edited. In just did them both as they looked like they had a similar function and my patience with this is running out so i just said screw it and just took all of the parameters down in both files. 2) I do not know what it does to other burning vehicle smoke in the game, as I have edited the shit out of everything pertaining to smoke in the last few days. Could someone back me up here and look at these two files, do some edits to see if you can see some improvement as well? Don't forget to back these files up first. I overlooked that. :) EDIT: By changing every parameter to 0 in JSmoke.cfg, I was able to eliminate the FPS drop completely. :) However... It crashes my system every time I exit the mission now. :( Could someone please post up JSmoke.cfg JSmoke2.cfg for me? Like I mentioned, I didn't back these up and I am going to have to edit and test line by line to see what parameter is causing the crash.. Thanks!

So this bug was introduced with this patch. Wednesday, 13 March 2013 We have released an update to DCS version 1.2.3.10201 that mostly focuses on localization and network stability changes: And this was included in the patch: Crashed and burning aircraft now produce smoke So, is it possible to see what files were changed with this latest patch. Maybe be able to single out something graphic/effect related that was changed? Or some way to do compare of the files somehow, and change them back to the original value prior? Or hell, just email the devs and ask them which files they were working on to add this smoke effect bug and what they changed so we can change it back, right? :hmm:

Tinted widows are present in Quad 1. We lost that, and wingtip vortices when A10C was assimilated into World.

With an inop hook and the crash barrier erected.

While I am familiar with the concept, I have somehow manged, until this point, to avoid watching a single minute of any Harlem Shake video. Damn it, Aries.. :)

Did you guys ever play Graphsim's Hornet Series or Janes FA18? Fantastic carrier ops in both of those. I remember playing Janes and it had carrier landing training missions. One of those, if I remember correctly, was really really hard. Pitching deck, black night, lightening. Really really challenging. I remember my buddies would come over and we would spend the evenings drinking beer, huddled around my comp, taking turns shooting carrier landings. Cheering each other on and talking smack.. Pretty damn fun. The Hornet is my second most favorite airplane of all time, so I am pretty excited to transition into a new jet.

Hey check it out.. Maybe on to something here: C:\Program Files\Eagle Dynamics\DCS World\Bazar\Effects\Jfx\Textures Inside of this folder you will find a bunch of smoke_ball .png files along with a test folder. That folder is 25MB in size and contains dupes of the smoke balls and other test files. I opened up the 6 smokeball files in the the texture folder in phototshop and all of them measured out to 2048x512 pixels at 72 dpi. Around 700KB in size. Do these file sizes sound right for typical graphic "sprites?" in game? To test that these maybe the files we are looking for, I deleted them, fired up DCS shot a truck and the game CTD. I put them back and all OK. Can someone with more knowledge about this stuff check out these files and see if something looks amiss? Gracias EDIT Ahh shit. Scratch all that.. These files are also present in standalone A10C. :crash: :(

Asus P6T, i7 975 @ 3.33, 6 GB DDR3, GTX295 (both GPU enabled) That'll do it, I would reckon. Thanks, Sith.

It would be interesting to know the specs of the system used to produce that movie..

It was introduced in the patch of the 1.2.3 update. Maybe related to this: Crashed and burning aircraft now produce smoke. It affects all burning units. It is not related to the boom1.lua particles settings. I also deleted that smoke smoke1.tga in the same expl directory and the smoke still appears, so I think that dir is a dead end. Took a two shots and zoomed in on exactly what the offending effect is. That is/was a burning truck. Look at the second screen shot of the almost dissipated smoke. It is still hammering the frame rate. That is the problem.

You add new features and get new bugs. How it should work: The beta testers find bugs, identify, then report them to be fixed by the developers. We are consumers, not beta testers. It is not our job. My copy of World and A10 C are not beta. These are the only modules that I chose to support and play. Fix my retail game, that was broken months ago by these "new features" and please and stop pushing untested or simply ignored beta code into it.

Thanks for looking into this, Mustang. I really hope you find a fix for us. Not sure how or why this this even made it into patch. It wasn't broken before, no one was complaining about not having thick plumes of smoke for downed aircraft.. Like someone just deliberately put it in there to break/disrupt playability... Makes no sense to me.

Does anyone know how to fix this? Is there a graphics file that I can delete? Who's idea was this in the first place anyway? Even one of the testers mentioned the day the patch came out that this was going to be an issue. I had to finally give up and leave a server last night it was just unplayable. The smoke FPS hit was so bad even my TIR was lagging. And the smoke was in the target area so imagine trying to get a mav lock on a ship at 6 FPS. Finally at 3 miles I was able to get a shot off. but was disintegrated by the three missile from the ship. How many months now have we had to deal with with the CBU/rocket/heavy gunfire/contrail framerate issues? It has been long enough. Fix your stuff, ED.:thumbdown:

That looks really, really good. Can't wait to fly this.!

Thank you for the confirmation and heads up, Dusty. I just tested the 87's.

Was sure hoping this was fixed. Are the devs just not seeing this issue? Or is it something that is just the way it's going to be from now on?

Study sim of the F15C.