Jump to content

RED

Members
  • Posts

    830
  • Joined

  • Last visited

Everything posted by RED

  1. I don't. Only with motion vector turned on. The artifacts I described might be different from what you are seeing. @dureiken
  2. yep Also recommend using the lates WQHL driver
  3. I had artifacts with motion vector on. It would basically look like the previous image would show again. This was not noticeable in general but text highlighted it at night and on the VR kneeboard. I turned it off in the WMR for SteamVR settings. There is no problem as frames below 45. Running the displays at 60hz causes stutters on my end.
  4. It should be fairly precise and together with corrected slewing relatively effective using AUTO and unguided munitions. For reference:
  5. For DCS, it's raw performance that is needed since there is no raytracing etc. You can compare numbers from benchmarks, ideally the ones that also run on DX11. Skipping the crazy OC numbers in Firestrike, I see around 40k GPU points for the 6700XT versus 33k of the 3060TI. As reference 6900XT ~60k and 3080TI ~48k.
  6. I just use the latest stable driver. One of the early beta drivers caused crashes. In benchmarks, the newer drivers improved performance, so there shouldn't be a reason to go back to an old one.
  7. For DCS, the HP Reverb G2 is still the go to headset. RTX3080/RX6800XT or better is recommended. Nausea will likely be there during the first couple of flights. For me it was really bad. If you immediately stop when you get sick you will get used to it. Currently I feel no effects from using VR. Other options are various headtracker using opentrack or the more expensive TrackIr.
  8. I didn't ask a question. The manual is pretty clear on this. There are approach lights on the nose gear and there is an AOA indexer inside the cockpit. As you pointed out correctly, the AOA indexer can be dimmed by a knob on the UFC. However the approach lights can be dimmed by the warning/caution/advisory light per the manual.
  9. As per title, track follows. See 2.6.1.6. Also just as a side note. All approach lights are different. The yellow sometimes looks like landing light in VR because it is so bright. Arg 84 in model viewer. 2D looks fine. Attached is a modeviewer shot (green is on) and one from a VR recording.
  10. @Petter1 It still says out of memory. If you are on steamvr beta, try the normal build. Set the preload radius to about a third of the maximum. Try again with all other apps closed and nothing running in the background. How much space to you have left on your drive?
  11. @Gourmand Check out these guides here: https://vr4dcs.com/ Generally the expectations you described for VR can only be met with higher performing hardware like draconus pointed out. The better your hardware is, the more you can crank up the resolution and game settings for better clarity. Many use the HP Reverb G2 without the need to zoom in or move closer to read something in the cockpit. With better settings you can get something like this: If you want to get better hardware, the best and cheapest way is to build your own PC.
  12. Just play a good old "clunk" sound when you would have hit your head.
  13. Ah yep, that makes sense. I was wondering about the fuel, too. I will check the start up with the manual. With "run away" i meant that it increased, normally you would say that it goes to the max and you can't trim it back. Thanks for you help. Good to have someone on the case before you even know I was in the front btw
  14. Did anyone report a runaway roll trim indicator for the EB? While using multicrew the trim indicator showed 20° left roll while the aircraft was actually trimmed out. We were not running out of trim and didn't test if the indicator was showing the actual trim setting. We also had a flap failure. Position of the flap lever was in sync and both cockpits showed flaps in travel but no failures. It first showed positions correctly and there was no control change or anything other than normal flight until the failure. I am chasing down a track but it will be very long. I can provide video to the devs though.
  15. Looked for a report but couldn't find one. You can't complete the run up as per checklist. Standby for track.
  16. RED

    Gallery

    Wow, great stuff!
  17. Not an expert on this but I'll try to answer some questions. The graph is actually FPSVRS's "History Viewer". Also seeing around 50% "usage" on the graph. It's normal that the most active cores change. The CPU is trying to spread the heat. On my end it's always moving between the two best cores. To compare CPU's a benchmark like cinebench helps. Here are some stock values from that benchmark: https://www.cpu-monkey.com/en/cpu_benchmark-cinebench_r20_single_core-9 This is the single core run and just what we want to look at with DCS. You can't compare frequencies between AMD and Intel. Currently the AMD CPUs get more done per cycle.
  18. Here is an example with a 5600X. Data from SP and MP on the Syria map: CPU frametime is around 12ms in MP and 9ms in SP. You have a good CPU bottleneck with 30+. I think it's time to upgrade your CPU, too. If you want to stick with it make sure you follow guides for reducing the windows overhead. Thud has some stuff: https://vr4dcs.com/2020/07/19/os-optimization-for-win-10-2004-key-tuning-for-dcs-world-and-vr/ I also upgraded from an older Intel CPU and it's a game changer.
  19. Running fine here with G2. Results are similar to that of the latest Nvidia cards.
  20. Just to give you guys an idea how it looks like: 2D screen is not ideal. I hope they find a solution in the future. The worst part is the animation for 2D where the camera moves towards the scope. Your head is kinda stuck to the right side inside the scope and it's really uncomfortable in VR when things are too close. Your instincts say to close the eyes.
  21. There were bios updates and I don't see many reports anymore. You probably have to be really unlucky to not get it to work at all. Most people seem to be able to fix it with usb cards if they have a problem with the mainboard. The cable of the Reverb is probably a bigger issue right now. It stops to work for some people with replacements taking a while.
  22. That works well according to many reports. If you want to pay even less, the Ryzen 5600X will give you the same performance with a 120$ mainboard and included stock cooler. That's what I did.
  23. Hey there, I get this when merging tracks: How can I prevent that?
  24. Using b550 and a 6900 XT here. Had an issue with some USB ports but overall it works well. It's tricky to get the performance where you want it but just getting video was almost plug&play. There is a keybind in DCS to reset head position. If you use that you don't have to hold your head still and can change seating postion anytime.
×
×
  • Create New...