

Cleric812
Members-
Posts
29 -
Joined
-
Last visited
About Cleric812
- Birthday 08/12/1989
Personal Information
-
Flight Simulators
DCS - IL2 BoS - P3D - MSFS
-
Location
Planet Earth
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Hey all, Been having a blast flying the MiG around the skies, just wondering if there is any setting I need to change to add a custom kneeboard? I have it sintalled in the "C:\Users\"User Name"\Saved Games\DCS\Kneeboard\MiG-29-Fulcrum" folder but it's not showing up. Reagrds, Vincent
-
Cleric812 started following 4K 32bit textures on all modules and DCS Crash in MP - secondary shadows
-
Hello all, Just got back from a total reinstall of DCS. The initial run using my previous settings resulted in a crash, however @Moezilla you managed to get it right, when I turn secondary shadows off, it runs just fine. So it would appear that there is a problem with the Fulcrum and secondary shadows. SSS, SSAO and SSLR all run fine, it seems to be just the secondary shadows which causes the issue. @BIGNEWY I hope this troubleshooting helps and the team can have a more focused look at this and see if they can fix the secondary shadows issue. Just to be complete I added my crash log for the crash after a total reinstall with the secondary shadows on. Now it's time to finally enjoy this gorgeous looking module and live my childhood fantasy Thank you all for the help and quick replies. Vincent dcs.log-20250919-070218.zip
-
Just tried it with SSLR off, no joy. Deleted the DCS saved games folder, still no joy dcs.log-20250918-165629.zip
-
Just a quick note, the thread is marked remove user mods. There are no mods installed at the moment whatsoever.
-
Just had a try after deleting the module and reinstalling it. It appears I discovered a new variable, it works in normal mode but not VR. Also DCS crashed in SP using VR so it would appear it might be related somehow to VR. Last display driver update was 4-5 days ago, running the latest nvidia drivers (581.29) Will try with SSLR off now.
-
Interesting, I have used some texture mods in the past but haven't done so since upgrading my pc to a new GPU. The mod was completely uninstalled and the MiG-29 was not yet released when I dabbled with texture mods. I also wanted to add that I did do a repair build earlier and deleted all shaders in the saved games folder. Neither of these steps helped. I will delete the MiG-29 files and redownload it. Seems odd this would cause a crash in MP but not in SP.
-
Hello all, I seem to be having a rather odd issue. Whenever I enter into any multiplayer server and select the MiG-29A Fulcrum my DCS locks up completely. Asking me to send a crash report, which I have multiple times. I can use other modules on the same servers without issue. I do see other players able to fly around in the new MiG-29A Fulcrum. I can use the module in SP, both instant action and training missions attempted. Has anyone experienced the same issues? If you need further info please let me know, I will add the crash reports to this message. Looking forward to flying this magnificent module soon since it has been my favorite since I first saw one years ago IRL, Kind regards, Vincent dcs.log-20250918-085805.zip dcs.log-20250918-093351.zip dcs.log-20250918-094021.zip dcs.log-20250918-105932.zip dcs.log-20250918-110453.zip dcs.log-20250918-111127.zip dcs.log-20250918-124810.zip
-
Hello all, I was looking into some stuttering issues today between textures High vs Medium and the culprit definitely is High textures on my system. However I noticed something else while checking the stats in the UI FPS info. In the line "Video mem(H/W) : xxxx.xMb/xxxx.xxMb (usage/budget)" the budget keep fluctuating between around 11.5Gb and 15.5Gb when using Medium textures my usage never exceeds these values but as soon as I bump it up to High it will exceed the 11.5Gb but not the 15.5Gb I have added some screenshots which show the fluctuation in budget. Is this indication in the stats perhaps showing a deeper issue now that the texture sizes of new modules are getting bigger and bigger? @NineLine and @BIGNEWY The difference in quality between High and Medium is barely noticeable in the CH-47 but in older modules like the UH-1 it is quite noticeable. Kind regards, Vincent van Veen DxDiag.txt
-
- 1
-
-
Hello all, I have an interesting issue with the CH-47. Whenever I do a cold and dark start as soon as I power o the RWR via the CDU I go from just about playable FPS to absolutely unplayable. The situation occurs both in MP and SP but is much worse in MP going from ~20-25 FPS to ~3FPS for several minutes before eventually resolving. In SP the fps returns to normal after around 10-15 sec but in MP it gets so bad it doesn't even register keystrokes anymore. I wonder if there are any issues related to the RWR? Kind regards, Vincent van Veen dcs.log DxDiag.txt MP.trk SP.trk
-
@BIGNEWY thank you for the reply and bringing this to the attention of the teams working hard to make our sim better. Don’t get me wrong, I love DCS and I just want to see the sim grow and be better.
-
So basically what I am getting from your post @BIGNEWY is that 4K 32 bit normal maps (and FLIR/roughmet textures) are intended to be this size and a huge drain on resources? I understand the desire for image quality but at what cost? Do ground units that I don't see from up close really need to have enormous files so that I take a nice looking screenshot of them? Since the other thread’s GPU's have gotten more VRAM sent we are again at the limits of what is possible with these unoptimised textures both at 4K screen resolutions and especially VR. I think the reason this feels frustrating to many is that using the script to reduce texture sizes proves the game is eating up enormous amounts of RAM and especially VRAM at high texture resolution. If I run the game with the default textures I run out of VRAM (all 16GB) nearly immediately. This leaves me with 3 options. 1. Use high texture resolution but run out of VRAM and encounter massive stuttering as the game constantly loads/unloads textures. 2. Use medium texture resolution, however now I cannot read my cockpit in certain modules since they are older and become blurry. 3. Manually alter my textures so I can use high but now I cannot join servers that require a pure client. I understand there is no pleasing everyone, but this optimisation which is sorely needed for the entire games texture library, would go a long way on alleviating all these RAM/VRAM issues. And just getting more RAM or a GPU with more VRAM is not a solution due to the costs involved. Brute forcing can only go so far. As has been suggested more than once. Perhaps the standard game should have these textures optimised and compressed using the optimal method for the texture’s purpose. And a separate pack be made available as DLC which allows users to go for super ultra high res textures for making a cool screenshot or video. Again the game can run and look amazing at high texture resolution IF the texture are better optimised. I understand this has been talked about many times. But I simply cannot see how this has not been addressed yet.
-
Hello all, Don’t mean to be annoying and bumping this thread but I never saw this one and I am honestly shocked to see this thread is so old already! The issue still persists to this day and is getting worse with every new module that is released! See: and: It would take less than an hour to run the script through a fully loaded (every module installed that is available) and it would reduce texture sizes by 60+ GB in total. This allows people to actually use high texture settings at high resolution and have all their cockpits readable since the older modules at medium settings are blurry. 4K 32bit textures are a total waste of resources if used for anything but the actual colour textures. And even then they would probably look just as good if they were compressed as DXT5 or similar saving so much memory both RAM/VRAM and disk space. Please have a look at this to try and improve and optimise the sim where it is sorely needed. @Flappie @BIGNEWY @NineLine It is not a handful of textures that are affected. There are hundreds of them that have to grown to ridiculous sizes that can be fixed in a matter of minutes using the script by @zbysiek Kind regards, Vincent van Veen
- 25 replies
-
- 16
-
-
-
Good afternoon, @zyll That is basically what I have been looking for for ages now! An automated way to get the file sizes in check! Thank you so much for pointing me in that direction I ran the script through my DCS folder and noticed the following results with regards to my original 4 points as laid out in the first post: 1. Less hard stuttering whenever I fly the CH-47, AH-64 or the OH-58 around the new Afghanistan map due to smaller textures being loaded in/out om memory or the SSD. 2. VRAM usage going to a manageable 13-14GB instead of instantly running to the 16GB which is the max on my GPU. RAM usage down from 40GB to 30GB. 3. Game loads slightly faster, though not a huge deal. 4. Total game size on SSD reduced from 861GB to 804GB. The texture conversion took my 5800X3D less than an hour to complete. The aircraft and cockpits look nearly identical and you really have to put them side by side to see the difference but the advantages are huge IMHO. @BIGNEWY and @NineLine This is not a huge ask of the team. This way we can still fly around using high texture settings with clear readable cockpits. It would be a huge deal if someone could please have a look at an optimized texture resolution and format option especially with the newer modules having ever larger texture file sizes. Even compressing all textures from 32bit to a much more manageable DXT5 or similar would be a plus. Can you please let us know if there is anyone looking into this? It shouldn't have to take 1,5 years plus to do what the community has done with the script and freely available tools (many thanks to @Zyll for pointing it out and @zbysiek for creating the awesome script) Kind regards, Vincent van Veen And two more shots from the AH-64
-
Hello all, Still no messages I see? I did some digging through the texture files and noticed every single texture is an uncompressed 32bit file. Again for normal maps, bump maps, roughmets and specular highlights this is not needed. It is using up valuable RAM, VRAM, and disk space. Don’t get me wrong, I do not want the game to go down in graphical fidelity. But these textures are a waste of space. And I know I can set my texture resolution to medium. This helps and is the only way I can actually run the game normally on my 6900XT with my Pimax Crystal, but the cockpits of older modules such as the F-5, UH-1 and Mi-8 are nearly unreadable and a blurry mess because the colour texture files are not high res enough. They are readable at texture resolution high. If there would be a real effort to optimise all these unnecessarily large and uncompressed texture the game could run so much better at the high texture resolution setting. I am currently not at my home PC but I will have a try at changing these textures to more suitable resolutions and post some before/after shots as well as run some benchmarks. Again @BIGNEWY and @NineLine I ask you to please take this to the developers. As well as third party devs and ask them to re-examine the texturing process. The way it is done now doesn’t work and needs optimising, badly, and has done so far well over a year. 65MB textures for the chair of the AH-64 alone doesn’t make any sense, nor does it make sense for ground units or the FLIR images. We are trying to fly a flight simulator, not take screenshots where the FPS and VRAM usage is irrelevant. Perhaps it would be an idea to offer people a chance to use the super over the top textures as an addon so they can choose to load up the sim to these unrealistic textures for screenshot taking? This way the rest of us who just want to fly can use the following: Colour textures 4096x4096xDXT5 Normal and Roughmet 2048x2048xDXT5 FLIR textures 1024x1024xDXT5 And a look at the damage model textures which are often huge, some even 8192x8129x32bit Sincerely, Vincent van Veen
-
Hello all, Just checking in to see if there’s any response? Brgds