Search the Community
Showing results for tags 'bit'.
Found 4 results
-
Hello all, I am sorry to be bringing up the same topic again as from months ago, however I feel it is still worth mentioning again and something that might help out a lot of people who are having issues since the latest few releases. As pointed out in a post in March 2023 by @Taz1004 a lot of the normal map, roughmet, and FLIR texture sizes in the game are absolutely huge. These texture files do not need to be this huge (22+MB and some reaching 64+MB) and are furthermore stored as uncompressed 32bit textures when they can easily be compressed without giving up any visual quality. The FLIR textures don't have to be 4K since all we ever see them through is our MFD's or similar sensors which do not have this resolution in the first place. The textures that are affected are mostly found in a lot of the newer modules but they are not exclusive to them. They are also not exclusive to player controlled modules or aircraft/helicopters. Ground units have the same issues. The issue also occurs with many off the addon modules not developed by ED themselves so perhaps a word from ED to the other developers to have a streamlined and standardized texture creation procedure could be considered? From what I can tell from some of the videos I have seen regarding the latest issues with stuttering many of us seem to be suffering from, it appears that DCS is trying to use as many cores as it can get to constantly load/unload textures between SSD->VRAM->RAM->page file leading to massive bottlenecks on the SSD side as the threads end up waiting on the SSD and thus each other. Perhaps one way to combat this issue would be to have the normal map, roughmet, and FLIR textures reduced in size which would, without sacrificing image quality; 1. Alleviate some of the bandwidth requirements between all these different components. 2. Reduce overall VRAM and RAM usage. 3. Reduce texture loading times. 4. Reduce the size of the sim itself (which stands at 861GB for me personally as I own nearly all modules and terrains). I totally understand the dev team is busy but if a modder can make these changes in a matter of a week or two it should be possible for the dev team to put someone on the task of hunting down these insane textures and make them a much more reasonable size. I implore you @BIGNEWY and @NineLine to please pass this message on to the responsible people and take another hard look at these texture files since this was first reported already over a year ago. As someone who has been using DCS since the days of LOMAC, please pass this on and take it seriously because I feel this could make the sim so much more enjoyable for many. Kind regards, Vincent van Veen
- 26 replies
-
- 22
-
-
-
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
- 26 replies
-
- 16
-
-
-
Pressing the BIT button on the RWR while the current RWR BIT is playing the missile launch audio or recycled missile launch audio will make it repeat infinitely until pressed again. Also, unknown if this is intentional, but you can run the RWR BIT before the display is turned on. F-16 RWR BIT Bug.trk
-
I have done a bunch of forum searching before posting this. Unfortunately, I haven't found an answer. Even checked Chuck's guide. When doing a cold start (land or sea), my NAV BIT for INS shows "NOT RDY". I believe I am aligning the jet properly, but at this point, I am starting to question that statement. Here's what I am seeing. From a cold jet on the carrier deck, I startup the engines and then turn my attention to the INS alignment. Step1 - Set INS knob to "CV" Step2 - Turn on STD HDG on HSI Step3 - Wait for QUAL:0.5 OK Step4 - Set INS Knob to IFA (yes, I am flying a mission in the GPS era) Step5 - Check NAV BIT QUESTION: Shouldn't the INS BIT now be something other than "NOT RDY"? The reason I ask is I flew a mission this morning after doing these steps above and my JDAMs were not accurate, nor was my targeting pod (it seemed to think targets were not where I marked them with the HMD (I did align that as well before flight)). I am starting to wonder if my INS alignment is incorrect. Sure this could all be piloting mistakes by me, but that NAV BIT is nagging at me. Am I missing a step in INS Alignment somewhere? Thanks.
