.jpg.33343a3cb04c263f039be6497ea5d01c.jpg)
mimamema
-
Posts
115 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by mimamema
-
-
21 hours ago, jurinko said:
Now I can run DCS with v63/Quest 3, starting it from the desktop icon or from Steam shortcut. I set SteamVR as OpenXR runtime and in game OpenXR toolkit still works. Strange is, now Turbo mode causes terrible stutter and DCS runs smoothly without it, before Turbo mode smoothed things out.
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.
-
11 hours ago, markturner1960 said:
I have version 63 of the oculus desktop software installed. I am using a Quest pro with a link cable through Quest link. Meta Quest link is set as the active OpenXR runtime according to my settings page. I start DCS using the following shortcut:
"C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --affinity=F
DCS and quad views both run fine...........Is this to be expected?
I just tried tried running DCS using "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_oculus_VR
And it runs, but quad views is not running.
So maybe this helps?
Also, as I seem to have an open XR runtime being used according to my oculus software, why would I need to add the shortcut above? What does it add that my first shortcut that includes affibity F and allows me to use quad views, does not?
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.
-
On 3/8/2024 at 11:24 PM, mrprime said:
I'm using the exact command arguments to switch to Oculus native API but still getting the crash with v63, wish I'd seen this sooner - looks like it auto-updated yesterday
I also have OpenXRToolkit and QuadViews .. I wouldn't expect those to work of course but I wonder if it's something in those which is still preventing the game launching.
Anyone with OXRTK/QuadView had any success with this work around?
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.
-
1
-
-
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.
-
1
-
-
5 hours ago, Hoirtel said:
--force_oculus_VR did work for me when I tried it.
Confirmed by openxr menu not displaying. I also have a foveated rendering and super sample applied in this tool which also did not load. I haven't kept using it as still on v62 but thought I would check it to make sure I could do it.
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.
-
39 minutes ago, jurinko said:
If I force oculus and still can open the openxr toolkit menu in game, am I running in openxr or in native oculus api?
That means you are not running Oculus VR, you are still using OpenXR
-
1
-
-
24 minutes ago, Qcumber said:
Yes. I realise that. I had thought my PC app had auto-updated after installing but it had not. This is the version I am using.
Edit: just reread my earlier post and it did not make sense. Sorry. I'll edit and update it.
null
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.
2 hours ago, BIGNEWY said:correct and thanks for confirming,
you have to be in MT DCS and not in openXR mode for native oculus to work.
@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.
-
14 minutes ago, Qcumber said:
I am using v63 in the desktop v62 in the desktop app. I thought my desktop app had updated so I guess I will keep this as is.
The link I am using is "D:\DCS World\bin-mt\DCS.exe" --force_oculus_VR
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!
-
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
-
2 hours ago, BIGNEWY said:
I will ask the team to check again. To be sure 1. are you using multithreading DCS 2. Not using OpenXR
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.
4 minutes ago, Qcumber said:The oculus_VR approach works for me. Just no open xr so I can't use OXRTK or QVFR.
Are you using v63 in your PC oculus app? Can you share the line you added to the shortcut for the us to test?
-
1
-
-
57 minutes ago, BIGNEWY said:
Work around is to use the native Oculus API or do not update to v63.thank you
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.
57 minutes ago, BIGNEWY said:Oculus made a change with v63 which has created this problem, and for a fix in DCS we will need to wait for the next patch.
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)
2 minutes ago, jurinko said:We can always get hotfix if v63 goes stable. That --force oculus vr thing does not work though.
I was hoping for something like this but not much after the answer I got above.
-
10 minutes ago, mbucchia said:
Oculus (OVR) isn't OpenXR, so none of your OpenXR mods will work in this configuration.
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.
-
9 hours ago, BIGNEWY said:
Sorry I am not sure as I don't have oculus myself.
What I do know is Oculus software update v63 is causing DCS not to start and the log will show the GPU is missing.
A fix has been made by us ready for the next DCS update.
thanks
@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.
-
34 minutes ago, jurinko said:
Edit: I swear since i have "force_oculus_VR" instead of "force_openXR" in the shortcut comment with v62 software, DCS runs smoother.
Yes, I´m not surprised by this to be honest, I will give it a go later on.
-
4 hours ago, BIGNEWY said:
Target line example in properties
"D:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_oculus_VR
hope that helps
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.
-
On 2/21/2024 at 1:47 PM, WirtsLegs said:
absolutely possible and not a overly difficult edit, check out line 1081 you will see where it checks for the name prefix, can change that to anything
However note that current iteration will only function on units that exist when the initialization script is run (so late spawned via script wont work)
also due to a DCS bug if the units in question are red or blue (not neutral) then they will ignore the stormtrooper orders if they detect a valid target within range, why I use neutral units for this usuallyThank 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
-
6 hours ago, BIGNEWY said:
Dear all,
By default DCS uses OpenXR which is supported by Oculus.For Multithreading DCS we also have a native Oculus API available which can be enabled by adding --force_oculus_VR
Due to the priority order OpenXR driver is selected first (prior to v62 oculus update) this was working well,
with Oculus v63 they broke OpenXR for DCS.
As a work around users can use native oculus with --force_oculus_VR
We do have a fix for the v63 driver coming in a future patch that will allow openXR to work correctly again for Oculus using the newer driver.
Thank you
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.
-
1
-
-
47 minutes ago, slughead said:
Same thing happened with SteamVR and Oculus v62. Steam had to fix it on their end. Looks like we are going to need a DCS side fix before Meta make this a general release.
Probably best not to mark this as solved… as it is going to come back when Meta push this out to all users.
Maybe we should continue with the issue in your report post. I will update my first post to explain the issue.
-
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
-
1
-
-
Just now, Reflected said:
I have automatic updates turned off
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
-
5 minutes ago, slughead said:
I have had this today and thought it was due to an Oculus update. I reverted back from the PTC to normal release of v62 and DCS loaded fine. I haven’t tried again with the PTC version of v62 however my DCS log ended exactly the same as yours has. I raised the error in VR bugs section. 2D worked ok though.
Oh, I noticed this as well, I going to try that as well. Thank you
Just now, Reflected said:The same thing started happening to me right now. I click on DCS, get the logging in message, then the loading screen then the exe disappears from the task manager. Tried a slow repair but didn't help.
Just waiting for oculus to downgrade to v62 again, if you use Oculus as well that might be the problem.
-
4 minutes ago, badatthis said:
i get that too, i think servers are down as if i use dcs normal not bata it comes us with log in blank and all my paines are cancelled
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.
-
4 minutes ago, silverdevil said:
can you also attach the crash zip that is in the same folder as the dcs.log? the log you provided does not show much info.
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.
-
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
-
3
-
DML - Mission Creation Toolbox [no Lua required]
in Scripting Tips, Tricks & Issues
Posted
As one of the main followers of his work, I can´t do anything else than agree with all that you have said about Dzsekeb and his work. Pretense is one the best free/public available PVE missions made for DCS and the closest one to a Dynamic Campaign we have ever had ( for the moment).
Mostly this is why months ago I asked you about the possibility of adding a logistic system into DML as I have always been looking forward to making a big mission "like" Pretense but with a little bit different mechanics and possibilities, and of course using DML as the main base of it as my coding skills are 0 to none
. That´s why I´m always having a look at this topic as I think DML has a lot of potential for all the people that find themselves in the same situation as me with 0 knowledge in coding but with some kind of will to create a bit more complicated missions. I think Dzsekeb, you and some others deserve a lot of recognition for the work you have done creating content and tools for all of us DCS enjoyers.
Looking forward to seeing what you are cooking for us in the next months/weeks if it finally gets out of the kitchen and am happy to test it as soon as it is available.
Thanks again for all your altruistic work.