Jump to content

mimamema

Members
  • Posts

    114
  • Joined

  • Last visited

Everything posted by mimamema

  1. That means you are using SteamVR instead or directly OculusVR which is like using Steam Link directly from your headset but using the cable. You must be losing a bit of performance cause of using both Oculus and Steam simultaneously. It makes sense that it works as it´s OculusVR v63 conflicting with DCS.
  2. Tried right now, and many other times, and it´s not working. Something is off here. Can you post a screenshot of your PC APP version? maybe it differs from the one I get with the PTC channel. V63 Oculus PC app and DCS are not compatible, I have tested it too many times. V62 works.
  3. I reported already that using Oculus VR with the v63 Oculus PC App was not working. Still, nothing has been said or modified about this post after warning BN about this issue. Steam Link and Virtual Desktop are working as they have nothing to do with the Oculus PC app, I prefer Steam Link as the quality it can deliver on my Quest Pro is closer to Oculus Link quality which is the best of all the options in my experience.
  4. Yes, the only problem is with Oculus link PC app, the rest should work as it normally does, actually, I made some tests with Steam Link and Quest Pro and it gives me better results than VD, and is quite close to Oculus Link.
  5. We are trying to workout if forcing oculus VR is working with v63, it was not for me, and nobody else has been able to confirm it working. In v62 is working already as you have confirmed now. But the issue is with v63 oculus pc app, that is the combination you need to confirm ( oculus VR and v63 oculus pc app), if not is going to be confusing for the developers to understand if it works or not. Thank you.
  6. That means you are not running Oculus VR, you are still using OpenXR
  7. Thank you for confirming this. It´s fine, don´t worry I could guess more or less what was happening. I would suggest not to update the app to v63 till we manage to clarify if the "force_oculus_VR" workaround works, but as far as I saw in other of your posts you use VD, so you should be fine with it. @BIGNEWY I´m sorry, this means that it´s not confirmed that works and the only experience we have for the moment is that is not working. I know you are not an Oculus user so I will try to make a small post later explaining what is exactly the issue here and what the people need to try and look for to see if the proposed solution works.
  8. Sorry, but I don´t understand which version are you using in the desktop app, meaning the one that I posted a screenshot above, could you post a screenshot of yours? I think you are confusing the version you have in your headset (mine is v63 as well) with the version of your Oculus Link app on your PC which is most probably v62 ( like in the screenshot I´m posting below). The problem we are discussing at the moment is related to the PC App that in v63 is not working with DCS, the version of the version of the headset has no incompatibility with DCS. So if you could double-check this it would be great. To double-check this please go to Settings in your Oculus App then open the General tab and scroll down as you can see in the second screenshot. Thank you!
  9. Tried right now (again, must be the 6th time), openXR as not the default openXR renderer ( as there´s no OpenXR mode) and in v63. And I´m using the shortcut in the screenshot ( that worked in v62). DCS does not open, it closes while in the splash screen. nullnull
  10. Hi, thank you for answering. 1. Yes I'm using MT. 2. That's the point of the line you are suggesting us to use, use oculusVR instead of OpenXR. To be more clear and as some others have pointed out in v62, if I add " --force_enable_VR --force_oculus_VR" it loads in oculusVR, and I know cause OpenXRtoolkit or quad views stopped working ( it's faster than looking at logs). If I update again to v63 and use the same modified shortcut DCS just doesn't open, same symptoms as the original report about this, the same as if we are using OpenXR. I have even tried disabling oculus as being the openXR renderer and it doesn't work either. 3. I'm one of the beta testers of Quad Views and VirtualDesktopXR, so I'm very happy to try any other solutions you can have in regard of this. I'm mostly doing this for the community that is not aware of all of this and I don't think they are going to like not being able to use DCS VR for the longer time that now a patch is taking to arrive to DCS. Are you using v63 in your PC oculus app? Can you share the line you added to the shortcut for the us to test?
  11. I´ve been reporting above that the workaround you are proposing (or whoever did, as I guess you are only the messenger) is not working on my end and afaik isn´t working for anyone else at the moment ( as nobody else has shown up saying is working for them), my intention was more to ask for possible a hotfix, I know where to look for the next update date already but thank you. Well, now that mentioned maybe you should have a look at what META says about the issue. Re: PTC v63 - DCS crashes on Link - Meta Community Forums - 1159560 (atmeta.com) I was hoping for something like this but not much after the answer I got above.
  12. I genuinely think this has nothing to do with OpenXR tbh, as trying to load DCS with Oculus VR isn´t working as well, at least on my end. But using Steam link or VD works ok with OpenXR. Anyway I could be wrong or not but with v63 stable releasing right at the moment is going to become a problem for a lot of DCS VR players that are not aware of this.
  13. @BIGNEWY When is this patch arriving?, as far as I know, Meta is already starting to release v63 as the stable version, and I can see a good bunch of VR users not very happy about it as using Oculus VR is not working either . TBH I thought the release of stable v63 was going to take longer. Hope you manage to fix this soon.
  14. Yes, I´m not surprised by this to be honest, I will give it a go later on.
  15. I already tried that line yesterday but I have tried again today and it is not working for me, I´m using Quest Pro but that should not really make a difference. I´m just testing it to avoid confusion with all those non-very computer-skilled users, as to me it´s quite easy to go back to v62 for the moment, and if that fix comes out before v63 becomes an official release then everything will be alright.
  16. Thank you for answering. Yes, then I don´t think it would work as I was planning, we will have to wait till ED sort out how IA shoot straight up to our foreheads
  17. Hello, I tried this right now and it´s not working with v63 at the moment. I tried the line that Skatezilla wrote in some posts above, and still behaves the same way, DCS closes while in the splash screen and that´s it.
  18. Maybe we should continue with the issue in your report post. I will update my first post to explain the issue.
  19. I can confirm this, this has just happened to me, I was having problems running DCS and after following @slugheadadvice of downgrading to V62 that shorted the problem. The only thing I could add is that the Oculus version in conflict with DCS VR is V63 which is only available in the Public Test Channel. null
  20. But do you use the Public Test Channel on Oculus? It worked for me, just opened it right now and it works. Thank you @slughead!!! That made my day, I was close to install a fresh copy of windows xD
  21. Oh, I noticed this as well, I going to try that as well. Thank you Just waiting for oculus to downgrade to v62 again, if you use Oculus as well that might be the problem.
  22. I don´t think so as I can see people from my squadron connecting, actually, the logging part seems okay on my side, it just goes through it without an error. But thank you anyway.
  23. Sorry, there is no crash zip from today's date in either of the folders, it just closes on its own without a crash window. I don´t if this should be reported somewhere else then.
  24. UPDATE--- PARTIALLY SOLVED: The reason for the problem has been found out here but it´s not really fixed, this happened because I´m an Oculus VR user and the last PTC update (V63) is producing a conflict with DCS. The workaround is to go back to v62 by deactivating the PTC option in your Oculus app on your PC and after downloading the proper version DCS will start to work again in DCS VR. To follow up on this problem there´s already a report in the VR BUGS sub-forum, here ----------------------------------------------------------------------------------------------------------------------------------------------------- (Original post before updating): So I was using DCS this afternoon normally and closed it. I tried to open it again tonight and it was not opening anymore. It crashes right after the DCS splash screen. I tried repairing and cleaning, renamed my DCSopenbeta folder, erased the temp files in local/temp folder, tried in MT and ST, firewall is offline right now and this is what my dcs.log says, not much and a screenshot of my event viewer. My PC is enough to run DCS (7800x3D, 4090, 64gb ram, 2tb SSD...), it´s just so random that now it doesn´t work but a few hours ago yes. I tried restarting the PC and the same, nvidia drivers are fresh from yesterday's update. Running out of ideas. dcs.lognull
  25. Hi!, amazing compilation of very different tools in here!. I was pretending to modify a Pretense mission to make use of the Stormtrooper function but then realized that I would have to modify loads of name groups just to only use this. Would it be possible modify the script so it looks for group names containing a specific word, like "supply" or "defense" instead of starting with AA_? I´m asking cause my knowledge of scripting is quite vague, I managed to understand more or less what it means throughout all the time that I have modifying mission but that mostly it, thit is all that I´m able to do at the moment. I know which line of the code the one is referring to the name of the groups but not what to change there. Anyway, thank you so much for sharing this with the community.
×
×
  • Create New...