Polite reminder, might be worth deleting the FXO and metashaders folders again

[Mr_sukebe]

Chaps,

I'm conscious that it was previously identified that the FXO and metashaders folders within our Saved Games folder were potentially causing some stutters due to the game engine addressing an ever increasing list of files. The easy solution being to delete the folders, which are then re-created by the game, but this time empty.

With the latest update, probably worth deleting them again.

Note that this will actually increase the load times on the first new load, but post that, should help.

[Ratcatcher]

Chaps,

I'm conscious that it was previously identified that the FXO and metashaders folders within our Saved Games folder were potentially causing some stutters due to the game engine addressing an ever increasing list of files. The easy solution being to delete the folders, which are then re-created by the game, but this time empty.

With the latest update, probably worth deleting them again.

Note that this will actually increase the load times on the first new load, but post that, should help.

 

Thank you! Excellent reminder.

 

I had indeed been suffering from this issue. (Along with my teamspeak playing up because of overwritten files).

 

Sometimes its easy to forget these little gems! :)

[Pteradon]

Thank you for this tip, Mr.Sukebe. :thumbup:

 

I've just tried this for the first time.

Did notice some longer loading times.

Ingame i had still some stutters, especialy looking to the ground while in flight.

[msalama]

I always delete them after an update, because I'll rather wait for a couple of minutes during the rebuild instead of potentially suffering all kinds of glitchy BS later.

[gianlu320]

Quick question

After 2.5.2 OB update 2 I deleted Fxo and metashaders2 folders thinking that DCS would recompile them as usual at the next start

But after I loaded the sim and used it I checked if the new files had been recompiled in Fxo and metashaders2

And I found metashaders2 folder empty

Nothing is there

But the sim works fine actually

Is this even possible?

Am I missing something?

Does DCS still use metashaders2 or not?

Also I remember in the past the folder was called metashaders and not metashaders2

Has something changed here also?

[BrainFart0]

Quick question

After 2.5.2 OB update 2 I deleted Fxo and metashaders2 folders thinking that DCS would recompile them as usual at the next start

But after I loaded the sim and used it I checked if the new files had been recompiled in Fxo and metashaders2

And I found metashaders2 folder empty

Nothing is there

But the sim works fine actually

Is this even possible?

Am I missing something?

Does DCS still use metashaders2 or not?

Also I remember in the past the folder was called metashaders and not metashaders2

Has something changed here also?

 

 

 

Yep, something changed. I also noticed that the metashaders2 stays empty since the 2.5.2 update.

 

Has something changed in how DCS is loading these shaders now?

[tarball]

Why does this manual "dance" persist if this is a known performance issue? Why wouldn't the game do this internally?

 

Just curious.

[BitMaster]

Why does this manual "dance" persist if this is a known performance issue? Why wouldn't the game do this internally?

 

Just curious.

 

indeed, valid question

 

I just delete them with every update since 2.5.x, better safe than BSOD

[rrohde]

I always delete them after an update, because I'll rather wait for a couple of minutes during the rebuild instead of potentially suffering all kinds of glitchy BS later.

 

Same here. :thumbup:

[Art-J]

Quick question

After 2.5.2 OB update 2 I deleted Fxo and metashaders2 folders thinking that DCS would recompile them as usual at the next start

But after I loaded the sim and used it I checked if the new files had been recompiled in Fxo and metashaders2

And I found metashaders2 folder empty

Nothing is there

But the sim works fine actually

Is this even possible?

Am I missing something?

Does DCS still use metashaders2 or not?

Also I remember in the past the folder was called metashaders and not metashaders2

Has something changed here also?

 

 

Might depend on maps you use. I've got some files being rebuilt in both folders, but I flew on all three maps (I don't own Gulf one) yesterday.

[gianlu320]

Might depend on maps you use. I've got some files being rebuilt in both folders, but I flew on all three maps (I don't own Gulf one) yesterday.

 

 

I’ve been using only PG since it’s release

But I have all of them

I need to try the others then

It’s a non problem since everything works fine for me

I was just curious to know if something changed

Thx

[sc_neo]

So you guys doing this regularly; do you actually see a performance difference when doing this nowadays?

[Art-J]

Not really, for me it's more of a precaution to minimize the amount of lighting and shading issues caused by frequent gfx engine tweaks in recent months patches.

[gianlu320]

I don’t see differences either

But devs reported it to be useful to avoid gfx problems so I do it as well after big updates as a precaution

[sc_neo]

actually for me, i just moved/deleted the fxo, metashaders and metashaders2 folders and the metashaders folder did not yet get recreated. Fxo and metashaders2 did. I started NTTR and Caucasus.

[gianlu320]

Yes I also confirm that metashader folder was not recreated on my pc as well

And Fxo and metashaders2 folder recreated but metashader2 is empty

I think is normal otherwise I guess there would be errors, instead my dcs world runs very nice and smooth

Edited June 11, 2018 by gianlu320
Errors in the text

[splash]

I deleted fxo, metashaders and metashaders2 and metashaders was not recreated.