Jump to content

niru27

Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by niru27

  1. Please refer to the thread title before sharing your opinion on "what is worth it" (for you). The issue is about bloat: the liveries cause a noticeable increase in storage space while not adding any meaningful value. FYI I have 2 separate installations of DCS (latest + older, more performant one with mods), so yeah it's not just about saving a few GBs, they add up and bloat the install. Don't forget they also consume extra VRAM when 4 jets next to you are using 4 different liveries. In the end, it has a net negative effect on everyone.
  2. I don't know what your local costs are, but for me a 4TB NVMe costs more than 64GB 6000MHz DDR5 kit. And I can't "enjoy" those liveries since I don't even own those modules, the only time I will ever see them is if I happen to spawn right next to them. Let's say ED puts all liveries into a "free downloadable liveries" module. You having to click one extra checkbox is an incovenience? And to rid you of that great burden, everybody else have to buy bigger SSDs? Don't you think people would rather use that money to upgrade to their RAM, than get a bigger SSD to store useless liveries only to accomodate your laziness? Unless both of you have outdated specs in your signatures, it's funny that you think it's prudent to spend more on SSD than on RAM
  3. I got shot down in an A10 C2 as well without the RWR going off
  4. I've given up any hope that this simple QoL feature will be implemented, and have switched to Open Kneeboard. Can be positioned anywhere you want and it will remember that setting You can add custom images/folders to show up in additional tabs, for e.g RWR codes, in-flight restart procedures, etc It shows radio log transcript history Supports multiple profiles, so you can have different customizations for different airframes and many more...
  5. As someone who doesn't care what livery someone else is using, I agree 100%. At the very lease those liveries should be made part of the module itself: if I buy the F14 for e.g. it implies I want to check out the different skins. If I don't, it implies I don't care for it. Forcing everyone to download skins for modules they don't own is just a waste of space.
  6. @Tom P you can use Open Kneeboard, it shows radio log transcript in one of the tabs, as well as MIZ briefing/slides
  7. Currently the rearm logic works as follows: No change in fuel level = rearm only Change in fuel level = first refuel, then rearm It would be nice if after RTB-ing we could first rearm, and then refuel, so that we get a few minutes to setup weapons, instead of just sitting there. It could be implemented in a few ways: Reverse the current logic: first rearm, and then refuel User settable option in game settings Check box in the rearm menu
  8. More complicated than flying virtual planes? If you managed to get DCS running, this is a walk in the park. True if you have only 1-2 modules and 1-2 devices. First you need to add a bind to each device to get the new UUID..... x 2 You need to copy-paste 2 x 2 = 4 times Then you need to add the modifiers back for each module But if you have FC3, that itself is 9 separate modules so you will do the above 9 x 2 = 18 times If you add a rudder then it becomes 9 x 3 = 27 times! Downloading and installing the pre-requisites for the script is a one time thing. Thereafter it's literally 3 steps to backup/restore no matter how many modules or devices you have: Select DCS Saved Games folder (should automatically be detected by script) Select Backup folder locationnull Press Backup/Import
  9. Did you not look at the GitHub link? It has step by step instructions with screenshots. Can't get simple than that
  10. It ain't so You can use my script to transfer binds from old PC to new one in just a few clicks: more info on this thread My script handles modifiers as well!
  11. Look for an x3D option, or buy parts and build it yourself. Even a 7800x3D will outperform Intel by a huge margin and at a lower price. And definitely get: 64GB ram (2 sticks of 32GB each, speed doesn't really matter for x3D CPUs) and a dedicated 1TB drive for DCS as recommended above
  12. If it ain't broken, don't fix it. Why do you feel the need for constant, unnecessary updates?
  13. The manual says: However in the jet: 1st press = Start timer 2nd press = freezes the timer DISPLAY, but the timer continues to run in the background 3rd press = unfreezes the timer DISPLAY, and shows the time elapsed since the 1st press F18_TIMER.trk
  14. So there are no unguided penetrators to destroy C3 bunkers?
  15. You can use this mission to reliably get CPU limited right at the (hot) start of the first mission, with a lot of activity. Was getting ~50fps with 12400 and went to 220+ with 9950x3D I always get GPU bound at the beginning of Raven One mission 2 "Riders on the Storm" But, with lower graphics, CPU gets additional headroom, and vice versa, so it is just a balancing act between CPU frame time and GPU frame time
  16. Ah that might explain why the focus region has lower detail with the same QV settings compared to VD Godlike.
  17. Using Intel Present Mon you can log GPU Busy, GPU Utilization % and total Frame Time. If Frame time > 13.89 and GPU Util > 100%, you're hitting GPU limits If Frame time > 13.89 and GPU Util < 95%, you're hitting CPU limits The problem in DCS is when there's a lot of units activity, it can spike CPU usage, so your frame time will go up. Perhaps we should tune settings to aim ~80% GPU usage so that we have headroom for sudden acitivities? -------- Have you tested how much CPU overhead QV adds? If you set peripheral to 1x and focus to 1x @ 0.01x0.01x, and compare that with QV disabled, that might tell us the minimum overhead required?
  18. Same, VD seems to look sharper to me somehow, while Pico Connect seems to have higher dynamic range and better colours. Is Quad View working on Pico Connect for you? When activated, it seems the entire view is at the peripheral resolution, and the hi-res focus region isn't drawn
  19. Your logic only applies to HDD. With SSD the data is never physically sequential since the controller has to do wear leveling, so it automatically moves the data to different parts of the flash memory. With HDD the data stays exactly where it was first saved, so the game files don't get "spread around" Further, the seek time for all sectors on a SSD is almost equal since there's no delay from a head having to physically move to the right place to read data, so it doesn't matter whether data is sequential or not. More importantly a human can't tell the difference between sequential and non sequential data reads.
  20. Got a new PC. The script helped to transfer keybinds easily
  21. Just run a slow repair on DCS, it will check all game files and redownload corrupt/missing files. This is the same as deleting + reinstalling DCS, except doesn't unnecessarily redownload everything. What makes a bigger difference is starting with a new Saved Games folder. Don't copy the old folder to the new PC. Start fresh. For keybinds you can use my script to automatically restore them on new PC:
  22. Ah, good to know. One day I might rewrite the script to fetch the UUID from here instead of external DLL
  23. Please follow the instructions on the Github What's the problem? Seems like your devices names got changed. Are current UUID's of connected devices always logged by DCS? In my script I have to use some DLLs to get that info
  24. You can use my script to automagically restore from your backup:
×
×
  • Create New...