Jump to content

Grodin

Members
  • Posts

    306
  • Joined

  • Last visited

Everything posted by Grodin

  1. It's not a performance issue, it's a maintenance issue. The plane can do 9G just fine, land based air forces have their hornets rated for 9G because they don't have to endure the stress of carrier landings so using a paddle is fine if you operate from an airfield and pretend it's a swiss, finnish or some other land based air force.
  2. Yeah this bug has been around pretty much since the burble was implemented, it's impossible to keep the nose up with it turned on, even full aft stick wont do - so just keep the burble off until its fixed :)
  3. Not aware of such websites but ive seen most people avarage around 60-65 when they start to get a hang of it, say around 100 landings or so - it's easy to get 75 every now and then but the occational 60 drops the avarage. More active players with thousands of landings seem to avarage around 70. I have 814 carrier landings (F14 and F18 combined) and last 20 landings i wrote down avaraged 66 with F14 and 69 with F18. Really depends on the squadrons you fly with, some take landings quite seriously and avarage much higher than some more relaxed squadrons. Also taking a break seems to hurt the scores, if i dont fly for a month i will struggle to get even 60 on the first 2-3 landings.
  4. I strongly recommend to make sure it won't come off accidentally, because when DCS thinks you took off your headset your flight will be done, the game will freeze and you have to restart. Once you get all the settings dialed in the only advantage G2 has is the center spot is ever so slightly more clear - i'd say like 10% or so. However with quest 3 you have that same clarity for all of your FOV, i don't have to turn my head at all or zoom in to read the texts in F16 MFD, all text is clearly visible from default head position for example (unless you use DLSS/DLAA which makes everything a blurry mess). FPS is same or better with Q3. Tracking is very much better on Q3. I'm on RTX 4080, 13900KS and 64gb DDR4 4400mhz CL18. Both - i max the settings in Oculus but also increase PD in DCS, because i can't use 2x MSAA, costs too much performance, but 1.2 PD is a good middle ground for image quality/performance. I didn't notice much difference in jitters or quality on Wireless desktop AV1 vs Oculus link on cable, but few random crashes on VD made me go back to cable - nothing like losing your progress after landing on 3 hour mission..
  5. Any news on DCS MT OpenXR with Reshade? Is it working?
  6. Thank you so much, you totally made me enjoy VR again! By default i felt like flying in a snow storm on my Quest 3, everything was blinding white from the ridiculous amount of haze. Now it is perfect, i think i'm going with 0.3 or 0.4. This should absolutely be a slider in the options!
  7. Can anyone confirm if current drivers fixed the vr issues and increased fps to 4080 levels where it should be?
  8. You can just tick the option from settings to override mission settings with your own i think.
  9. Considering that the landings work perfectly fine for the rest of us the only logical conclusion is that either a) Something wrong with the technique or b) something wrong with the game. I'm unable to reproduce a situation where the nose wont stay up no matter how heavy i load the plane if i have the correct AoA and glide path.
  10. Unlikely because any weight you can take off with you can also land with, there is no seperate landing weight limitation.
  11. I like how it feels now, it is better, however the well documented 60-80ms input lag (nothing to do with curves) still remains, anyone can confirm this by recording the gameplay at high fps and calculating how many frames it takes for the plane to respond to inputs - it takes a lot longer than other planes. I'm not debating if it is correct or not, but the input delay is there.
  12. They go long if you set the bomb settings for too high altitude, for example i had my bombs at the default 1500 ft and tried to drop them at 500 feet so they went long. After having correct altitude for the bomb settings they hit where they were supposed to.
  13. Could some quest 3 owner vefiry if F16 OSB button texts (HSD, TGP, WPN, SMS etc etc) are easily and clearly readable from the default head position or do you have to move closer to see them well? Trying to figure out how much clarity i would be losing if changing from G2 to Q3.
  14. Did disabling the toolkit give any benefits? Before 2.9 i never got reprojection working well, lots of ghosting and apache rotor causing issues etc - is motion reprojection better with dlss?
  15. With Reverb G2 i find DLSS unusable even with "Quality" preset, cockpits go so blurry i can't read labels, can't read F16 MFD texts and all fast moving things ghost horribly. Increasing pixel density helps for the clarity but whats the point because then i lose all the performance i gained to begin with.
  16. In this track you seem to use a keybind to open "intercom" which is a keybind called "open communications menu", that does not work unless you use easy comms options i guess? Try using keybind for "Transmit switch" there is one for UHF and one for VHF. You need to select which radio you want to use - all i can think of is that you are used to the "easy comms" option and either they are phasing it out or it is bugged, i can't really help you with that as i don't know how it is supposed to work.
  17. Only thing i could think of is that maybe you are already slow enough when touching down that the nose wont stay up? Sure it does fall down a bit sooner with heavy weight, but i can always keep the nose up atleast for a while even if landing with max load, but i land at 11 AoA instead of the 13 so i might be coming in a bit faster than you.
  18. Assuming you are not using "easy comms" option you have PTT Button for VHF and PTT Button for UHF, you need to press one or the other depending which radio you want to use to contact the tower or whoever you want. I don't mean you have to keep pressing it when using AI radio commands but just press it to open the comms menu. It makes a difference which radio button you use to open the comms menu. Also pay atenttion that you can tune the radio to either a preset channel like 1, 2 or 3 for example or manual frequency.
  19. Yeah - unfortunately the way they implemented it in DCS has same issues as MSFS for example, any fast movements will be horribly ghosted, F18 fuel numbers for example and even on highest settings all of these make cockpit very blurry, don't find them usable in VR. There used to be a shader/plugin mod "3dmigoto" or something that allowed FXAA in a way thay only covered things outside the cockpit, that was perfect, but doesnt work anymore. In F16 i cant read any text from the screens and barely any labels without leaning forward with any of these new AA/DLSS/FSR settings but without any AA they are crystal clear. Hoped this would help me go from steady 60 fps to 90 fps with RTX3090 but i guess i just need to start saving for 4090, heh.
  20. In vr the new spots are gigantic. At first i tought i have lots of dark puffy clouds in the horizon but they ended up being these new spots.
  21. Adding DLSS to an old engine and in a way that is actually useful - meaning the cockpit is not affected must be a huge task and i hope ED takes as long as it takes to get it right because proper DLSS implementation seems to be our only hope for great VR performance before we get Vulkan. Thanks for letting us know in advance if there will be a patch or not in advance, i plan to take the whole weekend off to enjoy it when it drops!
  22. Are you misunderstanding him on purpose? Because i completely get what he is saying and thats not it. While the current cockpit might be realistic when playing with high resolution etc there are many occasions where that is not the case and the end result is not that great because stuff in the cockpit is a bit challenging to read even with large screens @4k and max settings. If the player is not very familiar with the cockpit and labels and hes trying to read the labels looking for some buttons as a new pilot with avarage hardware and settings or a vr headset with avarage resolution the experience might not be that great if you have to spend too much time trying to figure out whats written on some label. And maybe some people just like to look at new fresh looking cockpits, now they can. Thats why we have options to turn on and off things we like or don't like - it's not a type rated sim, you can do whatever you enjoy doing with it and it's nobodys business if someone thinks its "correct" or not. No matter how difficult or unpleasant it is we are all still just sitting in front of a computer playing a game and enjoying our time, forcing someone to look at something they don't enjoy seems pointless. Luckily we have this mod and everyone can be happy - those who like it can use it and those who dont like it don't have to use it.
  23. Its night and day also for 3080ti vs 3090 because 3080ti runs out of vram in dcs vr causing it to run poorly.
  24. Interesting i'll try it too when i get home. Very little drop in the real takeoffs indeed.
  25. Do you have enough headwind, is the ship moving? Turn the ship towards the wind like they often are in reality and you might see quite a bit less drop.
×
×
  • Create New...