Jump to content

Recommended Posts

Posted

I'm also aware of a new dis-connect in the saved games pathing,

if you're on ED DCS OpenBeta Branch, it will update and use \Saved Games\DCS, instead of \Saved Games\DCS.OpenBeta\

I will revise the auto detecting of the paths for openbeta if version > DCS_UNIFIED, but until then, you can prolly use dcs_variant.txt file to point the Sim back to the \DCS.openbeta\

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
1 ora fa, SkateZilla ha scritto:
Cita

Once the settings file is saved, click Dedicated Server Mode, it will launch the process, which would take a few minutes to load, then launch the WebGUI and allow it to connect to the server.

I will wait for new updates because at the moment I can't get it to work. Thank you. 

 

 

S.O: Win 64bit
MB: ASUSTek TUF GAMING X570P/Alim: 850 watt Corsair 850TXEU
CPU: AMD Ryzen 7 5800X3D 8 Core/GPU: nVidia RTX3070 8GB (GIGABYTE Technology)
RAM: DDR4 64 GB 1600Mhz
Accessories: Thrustmaster Hotas Warthog

Posted
17 hours ago, Mav87th said:

Request for new feature..... 😉

 

Added possibility to launch the "Model Viewer" from the binMT

It's integrated internally, I had to wait for MT ModelViewer to be stable.

  • Like 1

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted (edited)

Is it normal behavior for the DCS-Updater to perform an update check, then auto switch to the Repair function (say, if the updater noticed something off)?  I typically use the your (Skatezilla) Launcher (2.0.0.37, Bld 10.20.2023) which is incredibly awesome.  Today I used it to do an update check... and the above happened.  Repair is happening now (not a bad thing) but I don't remember ever having the Repair function start without telling it to do so, whether using your Launcher or the DCS-Updater.   Not sure if it's the Updater, Launcher, or has something to do with the disk location move.

Friday, due to the update size, I had to move DCS to another drive.  Started the game numerous times over the weekend but not sure if I checked for an update since then.  So maybe that's something to do with it.  I did change the target locations in the Launcher.

Just trying to find if this is normal.

Edited by Mikkall
Posted (edited)
On 2/26/2024 at 1:58 PM, Mikkall said:

Is it normal behavior for the DCS-Updater to perform an update check, then auto switch to the Repair function (say, if the updater noticed something off)?  I typically use the your (Skatezilla) Launcher (2.0.0.37, Bld 10.20.2023) which is incredibly awesome.  Today I used it to do an update check... and the above happened.  Repair is happening now (not a bad thing) but I don't remember ever having the Repair function start without telling it to do so, whether using your Launcher or the DCS-Updater.   Not sure if it's the Updater, Launcher, or has something to do with the disk location move.

Friday, due to the update size, I had to move DCS to another drive.  Started the game numerous times over the weekend but not sure if I checked for an update since then.  So maybe that's something to do with it.  I did change the target locations in the Launcher.

Just trying to find if this is normal.

 

the only time my app would launch repair,
is if user set the advanced options to purge shader cache and re-compile them after update.


Also the next public update wont be until ED's next patch likely,
as there is a significant amount of re-writing under the hood being done due to branch restructuring.

plus a bunch of other things I wont get into, but alas the current change log, even after purging testing related items is over 200 Lines.

Edited by SkateZilla

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
13 hours ago, MAXsenna said:

You don't. Use add remove programs in Windows.

Sent from my SM-A536B using Tapatalk
 

OK, thank you for answering. Have a nice day.

  • Like 1
Posted (edited)

When you move your mouse over one of the Build Slots, you can right click it to set the paths for the DCS directory and for your Saved Games directory.

image.png

Edited by Lange_666

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Posted

So I have only recently wanted to use two different profiles in the Launcher. I have saved the app config and when i load it back up, it shows the specific profile paths I want to use with that specific slot, but when i load the game using the "Launch VR OFF" button it seems to create a profile in DCS.openbeta. Is there a way to stop this form doing that?

 

CPU: i9-12900K @ 4.9Ghz

M/B: MSI MEG z690 Ace

RAM: 128GB

Video Card: MSI RTX 4090 Suprim Liquid X

VR: Varjo Aero

Posted

so was able to verify that -w "PROFILENAME" still functions correctly as a shortcut, but selecting the different profiles seems to only load the DCS.openbeta folder even if there is another path specified.

CPU: i9-12900K @ 4.9Ghz

M/B: MSI MEG z690 Ace

RAM: 128GB

Video Card: MSI RTX 4090 Suprim Liquid X

VR: Varjo Aero

Posted
16 hours ago, boapiu said:

oops. as soon as I set the path, or try to, the app crashes. are there any instructions?

where are you setting the path too?

This behavior sounds like the file path exception bug I've fixed internally, when you point to a directory incorrectly as it crashes looking for files that arent there.

Should be pointing to \DCS World\ root...  not \Bin\ or \Bin-mt\ etc.

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted

Good day, I am reaching out for a little help.

 

I have oculus rift s.  Yesterday all was good.  Today when I try to start DCS, either through this launcher with VR on, or through the desk top icon, it crashes on the load, with only the start icon appearing below then disappearing.

If I start with this utility with VR off, it flashes up right away.

Any idea what the gremlin may be between DCS and starting in RIFT S VR?.  Like I said, this is the first time this glitch has reared its ugly head since I reloaded the game months ago.  All good until trying to flash up today.  Curses!!!

Any advice appreciated.

Wally.

 

Screenshot 2024-03-08 200740.png

Sometimes I get this far into the boot up, but then it stops.

Screenshot 2024-03-08 201552.png

Posted

Disregard my VR problems, I found this is a common issue on thread. 

 Latest Oculus v63 PTC build crashing DCS when used on Oculus Link

However, if you have an idea on how to fix, please share.

Posted (edited)

Probably nothing if you upgraded to Oculus v63 because v63 PTC is rolled out into release and the problem started there.
ED needs to come with an update.

Edited by Lange_666
  • Like 1

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Posted (edited)
9 hours ago, majorandme said:

Disregard my VR problems, I found this is a common issue on thread. 

 Latest Oculus v63 PTC build crashing DCS when used on Oculus Link

However, if you have an idea on how to fix, please share.

Change the API to Oculus API in th4e Adv. Launcher Page.

4 hours ago, Lange_666 said:

Probably nothing if you upgraded to Oculus v63 because v63 PTC is rolled out into release and the problem started there.
ED needs to come with an update.

 

ED has a fix internally from what they've said, However, they are not required to rush any updates to fix something Meta broke themselves. Plus there is a alternate launch method that side steps the problem *Using Oculus Runtimes instead of OpenXR.

ED Rushing a update will not fix the problem with 75% of Meta's own library apps crashing with the same problem.

Meta's QA team seriously dropped the ball on this, as the problem was reported in their tester forums long before it went to preview and release builds.

Edited by SkateZilla
  • Like 1

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
11 hours ago, SkateZilla said:

Change the API to Oculus API in th4e Adv. Launcher Page.

ED has a fix internally from what they've said, However, they are not required to rush any updates to fix something Meta broke themselves. Plus there is a alternate launch method that side steps the problem *Using Oculus Runtimes instead of OpenXR.

ED Rushing a update will not fix the problem with 75% of Meta's own library apps crashing with the same problem.

Meta's QA team seriously dropped the ball on this, as the problem was reported in their tester forums long before it went to preview and release builds.

 

No effect.  Crashes on boot up, except if SteamVR selected, then it opens in 2D

Posted
12 hours ago, majorandme said:

No effect.  Crashes on boot up, except if SteamVR selected, then it opens in 2D

I will check the behavior on my end in debug mode, but it maybe a argument issue w/ the launcher.

I will also check w/ Meta, as they might be putting out a patch or rollback instructions, 

I think it *ONLY* effects Quest I II II through Oculus Link, they integrated changes that causes the Headset to timeout and crash the app using it and / or the Display driver.

  • Like 1

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
2 hours ago, SkateZilla said:

I will check the behavior on my end in debug mode, but it maybe a argument issue w/ the launcher.

I will also check w/ Meta, as they might be putting out a patch or rollback instructions, 

I think it *ONLY* effects Quest I II II through Oculus Link, they integrated changes that causes the Headset to timeout and crash the app using it and / or the Display driver.

Thanks Z.  Appreciated.  BTW, I have a cable Rift S.  I can launch with VR off, but when VR on, as soon as DCS tries to boot or connect to Oculus, DCS crashes. 

Posted
On 3/9/2024 at 12:22 PM, SkateZilla said:

Meta's QA team seriously dropped the ball on this, as the problem was reported in their tester forums long before it went to preview and release builds.

The real question should be: did anybody who is not Meta's AI noticed the bug and reported it in the tracking system... And also how widespread the issue is.

BTW, is it possible to launch different external apps based on the selected profile? E.g launch oculus for VR and trackir for default? 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...