Jump to content

bwRavencl

Members
  • Content Count

    41
  • Joined

  • Last visited

About bwRavencl

  • Rank
    Junior Member
  • Birthday 07/28/1989

Personal Information

  • Flight Simulators
    DCS, IL-2, BMS, X-Plane, Prepar3D, MSFS
  • Location
    Kempten, Germany
  • Occupation
    Software Developer
  • Website
    https://bwravencl.de
  1. Solution and potential bug in DCS After trying all sorts of stuff I finally found a workaround for the huge performance loss I experienced after the 2004 update. Since I'm pretty sure other people will run into the same issue after installing the Windows update I am documenting my findings here. Also I believe my observations are pretty indicative of some pretty deeply hidden bug that could be the cause for all kinds of severe performance problems. That's why I think this should definately be looked at by a developer and be made into a bug report. Consequently I will recap my observ
  2. Horrible FPS and stuttering after updating to Windows 10 2004 After installing the 2004 feature update FPS in DCS are extremely low and unstable for me. I'm running an Intel i7 8700, 32GB of RAM and an RTX 2080. My system usually easily hits 60 FPS, especially after the latest DCS Open Beta Update performance was pretty good overall. However after installing the 2004 feature update DCS barely hits 35 FPS. I already tried all the usual stuff: reinstalling the NVIDIA driver, different driver versions, deleting shaders, enabling and disabling the new GPU scheduling feature, etc. Nothi
  3. +1 :thumbsup: I also would love to see double seater variants of both the Hornet and the Viper in DCS. Even without any additional functionality they would increase overall variety. I would even pay for these double seater models if they came as an expansion for the current modules.
  4. I was unable to find a keyboard binding for the rudder / yaw trim switch, seems like it is missing...
  5. This is just the default viewpoint, you can change it permanently by first adjusting the zoom and / or viewposition as you like it and then press Right Alt + 0 (on the NUM-Pad).
  6. That's exactly what I was thinking when I read about the concerns. :thumbup:
  7. +1 Also I believe everybody woud appreciate it if we could get clickable throttles not only for the Hornet but also for the Viper and generally for all (future) modules for which this applies as well.
  8. I also would love to see the A model for cold war era missions. However as I see it itˋs rather unlikely that ED will invest into an A variant, as it is a vastly different aircraft and would still require a lot of development time, even if the Block 50 is fully implemented. There would probably be some people like us that would happily pay the full price for this, but I guess the majority of the customers out there would rather have an entirely different aircraft to invest their money in after the Block 50.
  9. Would be handy if we could also get a click-spot to hide it like in the Hornet.
  10. An Extra 300 with a well made PFM in DCS would be awesome!
  11. Yes I am heaving the same issues. 1. Sensor Select Right does not exit ACM mode 2. When in AACQ mode and hitting Sensor Select Down, then Undesignate, the radar stays in an 8 degree scan mode. Now if you increase the scan zone by clicking the corresponding button on the MFCD, you can choose invalid scan zones, such as 252° (screenshot). After switching through the scan zone sizes multiple times by clicking the MFCD button it will return to the allowed values eventually and remain within the allowed set, unless you provoke it again.
  12. Check out this thread: https://forums.eagle.ru/showthread.php?p=3476910 It seems to have multiple functions, but during the EA phase it will probably be pretty useless.
  13. Afaik it can be used by the pilot to place an event mark in the avionics log, to help the maintenance crew find the cause of a potential anomaly.
×
×
  • Create New...