Jump to content

The DCS Updater / Launcher GUI Utility Version 2.0 (2023+)


Recommended Posts

6 hours ago, Monarch said:

Is there still no way to update the launcher from the launcher itself? I still have the auto-update function hard locked to disabled so just curious

No, not until I resolve a majority of the core bugs and UI. (And find a suitable host for app deployment).

2 hours ago, calys said:

Hi everyone, I wanted to know how can I use the "Dedicades Server" function? Even after filling in the server data, I can't get it to start. Where am I going wrong? Thanks

Immagine 2024-02-24 091434.png

 

 

 

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.

Also you have Standard, 2D, and VR on, as well as WebGUI Mode, those settings are conflicting with each other.
WebGUI Mode disables 2D and VR as well as the standard Server window.

  • Thanks 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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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. 

 

 

[sIGPIC][/sIGPIC]

 

S.O: Win 64bit

MB: ASUSTek TUF GAMING X570P

CPU: AMD Ryzen 7 3800X 8 Core

GPU: nVidia GTX1080Ti 8GB

HD: Sabrent SSD 1TB

RAM: DDR4 32 GB 1600Mhz

Accessories: Thrustmaster Hotas Warthog

Alim: 850 watt Corsair 850TXEU

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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
Link to comment
Share on other sites

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

Link to comment
Share on other sites

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 combat pedals, TrackIR4, Rift-S.

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 combat pedals, TrackIR4, Rift-S.

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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. 

Link to comment
Share on other sites

  • Recently Browsing   1 member

×
×
  • Create New...