Jump to content

some1

Members
 View Profile  See their activity

  • Posts

    3451

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Everything posted by some1

  1. some1
    I agree that the gunsight currently does not provide enough lead even if the target is turning at a meagre 2 or 3 g. The bullets always fly behind the target, until you get so close that the error does not matter any more.
  2. some1
    To my knowledge F-4 variants will be separate purchases (at least the Navy and USAF variants), while Aerges planned several variants from the beginning and priced their product accordingly from the start. Whatever money Beczl/Leatherneck/Magnitude made from all the sales over the years, it's probably not enough to fund another variant for free. Also, other MiG-21 variants are indeed quite different from each other and would have to be treated basically as separate airplanes, especially the three that you've mentioned.
  3. some1
    I know it's a bit late, but thanks. And congratulations. Of all the developers that had this issue reported in their aircraft at the same time (ED, Heatblur, Razbam, Leatherneck), to this day you're the only team that fixed it.
  4. some1
    If anyone's interested, here's a short track presenting AI CH-47 that survived: - three hits with IGLA followed by: - six hits with Vihkr followed by: - multiple hits with 30mm HE I put him on fire - twice - yet he was still able to pull manoeuvres that put Ka-50 agility to shame. I don't think IGLA warhead damage is our only problem here... immortalCH47.trk
  5. some1
    When following the limits displayed on the Engine Power Indicator, Ka-50 shows much worse performance than Mi-8 and Mi-24. For example here's a test hovering with engine power at 'H' setting (max continuous). Same conditions, same weight (9.9 t). Antiice and air filters off: Ka-50, with supposedly the most efficient rotor system: barely lifts off the ground at 1m/s and can only hover in ground effect. PTIT: 855C, EPI 7.5, engine RPM 96% Mi-24 with supposedly the same TV3-117VMA engines, climbs initially at 6 m/s, still climbs above 1 km altitude at 4 m/s: PTIT 920C, EPI 7.8, engine RPM 97%. Mi-8 with the weaker TV3-117VM engines, goes like a rocket at 10 m/s and barely slows down, at 1 km altitude climbs 2x faster than Mi-24. PTIT 890C, EPI 8.2, engine RPM 96%. The same is with horizontal flight, max speed at 'H' max continuous power is roughly: Mi-24: 160 kts Mi-8: 155 kts Ka-50: 135 kts Note the much lower PTIT temperature in Ka-50 at 'H' setting. Looks like either the power limits displayed on the indicator are too low, or some helicopters in DCS are over/underpowered. climbTest_mi24.trk climbTest_mi8.trk climbTest_Ka50.trk
  6. some1
    You forgot to explain that in the previous post. Dropping numbers like that without explanation might as well suggest OP that there's something wrong with his PC or cooling.
  7. some1
    Which is apples to oranges comparison. This drops the temperatures by 10-15C.
  8. some1
    5800X3D tend to run hot due to construction. It's not that the CPU produces much heat, but rather the extra cache acts as an insulator. Temps in the range of ~80 degrees when gaming and hitting 90 with Cinebench are nothing uncommon, though it depends on the particular unit and motherboard combination. Some people get much better temps even on the same hardware, it's a lottery.
  9. some1
    1. update your bios 2. if that doesn't help, try different usb port 3. if that doesn't help, try downgrading PCIE from 4.0 to 3.0 in BIOS, and try different USB ports again 4. If that doesn't help, maybe external USB hub will.
  10. some1
    This can happen if you load a mission with fog.
  11. some1
    If I go into the front cockpit and manually play with the sights, then after I'm back to piloting the helicopter, Petrovitch is unable to find targets any more. I think it's related to sight zoom level, because I managed to "fix" it in the attached track by changing the zoom level back to wide angle. 1st attempt at searching for targets after taking off - Petro OK. 2nd attempt at searching for targets after changing sight zoom to narrow FOV - Petro Blind 3rd attempt at searching for targets after changing sight zoom to wide FOV - Petro Ok again PetroBlind.trk
  12. some1
    The issue is back, IHADSS brightness starts to flicker whenever rotors get in the field of view (or close by).
  13. some1
    Thanks for the write up. Yeah, I don't know what combination of settings causes such difference on my system, but I did several test and it always came out like that. Back when I used RTX3080, both were about equal in performance. SteamVR always offered better reprojection quality, as you've pointed out.
  14. some1
    In case you guys haven't noticed, there have been some updates to WMR for SteamVR software recently that claim to fix some stability and performance issues. May be worth checking out if you switched to OpenXR. As at least on my system with RTX4090, I get noticeably better FPS with SteamVR now than with OpenXR at the same 140% resolution on Reverb G2. Where OpenXR makes 80 with GPU loaded to the max, SteamVR can hold 90 fps with some room to spare. https://store.steampowered.com/news/app/719950/view/3680036899858715469?l=english
  15. some1
    I just use OpenComposite runtime switcher. If I press the "switch to OpenComposite" button in that program, it's using OXR. If I start SteamVR after that, it automatically switches back to SVR. It's the opposite for me. In the same spot where SteamVR produces 90 fps with a hefty headroom, in OpenXR I barely get 80 fps at noticeably higher GPU usage. That's at the same resolution per-eye (140%) and without any upscaling/FSR, as these work differently in each runtime so they are not really comparable. For what it's worth, I have "optimize rendering" option checked in WMR for SteamVR software, and HAGS is disabled in Windows settings, VR really doesn't like it. (not my screenshot, ignore other options).
  16. some1
    Short question, have you tried SteamVR instead of OpenXR lately? When I checked, I got better performance with 4090 on steamVR, it received some stability and performance improvements no so long ago.
  17. some1
    Looking at CPU utilization is useless for games, because it will show 100% only if all cores are fully loaded. Which is rare for any game, and especially for DCS that is still mostly limited to 1-2 cores. A more meaningful metric is GPU usage. If GPU usage is not close to 100%, then CPU/memory is the limit.
  18. some1

    DLSS in DCS

    some1 replied to Supmua's topic in Virtual Reality

    People may confuse two things. The Frame Generation feature introduced in DLSS3 for RTX4000 series cards will not work in VR. But the DLSS itself (antialiasing and upscaling) works just fine. It may not produce image quality to your liking, but that's another matter.
  19. some1
    Your Ryzen 3700x is THAT old. Best course of action would be to change it to 5800X3D, which should be compatible with your motherboard. It's sold at some pretty discounts lately. If you want to be sure, chekc FPS VR or OpenXR debug statistics (depending on which runtime you use) and check if CPU frametimes are higher than GPU frametimes. That's an indicator of CPU bottleneck in VR.
  20. some1
    Yes, it's noticeably lighter, but at the cost of being more prone to slide on the desk, unless you mount it or use the included suction cups. In the Warthog throttle iirc most of the weight is in the bottom plate, you can remove it and replace it with something lighter.
  21. some1
    In this case you're testing GPU limits, not CPU. Not a bad thing to do, just different. For me the GPU usage in this spot does not ever reach 100%, so my FPS measurements are limited by CPU.
  22. some1
    What's your gpu usage with all shadows off? 100% or less?
  23. some1
    Ok, I tested the same spot on High preset but with All shadows disabled (both terrain objects and main shadows setting to OFF), and the performance of both 2.7 and 2.8 is the same, hovering around 180 FPS. And looks like I'm still on CPU limit, so GPU is not skewing the result. I guess that is a good news, it shows that the shadows are indeed the main culprit of increased CPU usage in 2.8.
  24. some1
    In a situation where you are cpu limited, cranking up a gpu intensive option will not have a noticeable effect. I could increase resolution or msaa, and it also wouldn't decrease framerate, at least not in that spot. Besides, it's not that Default option has no penalty on the cpu, more likely the cost of extra objects added with shadows OFF negates the gains from not displaying shadows. Maybe tomorrow I'll check how are the numbers with all shadows off, including self shadowing and cockpit. That should reduce the object count.
  25. some1
    Default shadows are not free, they put more load on GPU. In this particular spot and with an RTX4090, the GPU has extra power to spare, so they don't make a big dent in FPS. Doesn't mean it's always like that. You can see this difference between various options better in the screenshots from VR that I posted on the previous page. Gpu frametimes are the worst with Default shadows, Flat shadows reduce GPU frametimes but increase CPU frametimes. Setting the shadows to OFF reduces both, but not by much. CPU Frametimes without objects shadows in 2.8 are still higher than in 2.7 with shadows on.
×
×
  • Create New...