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

[Cibit]

Nice one :thumbup:

[tarball]

when is this new version good to go?

[SkateZilla]

when is this new version good to go?

 

it's in extended testing, the new version is a very big step up, the code changes need tested extensively,

 

Just today I found mistakes/conflicts in the detection code and had to revise it a few times to resolve issues.

[Svsmokey]

Many thanks

 

Many , many thanks for this !

[SkateZilla]

Still testing and finding bugs,

 

So far I'm finding lil ones almost daily,

 

Today I found an exception bug that requires me to recode the Network/Servers Check Blocks.

 

Update: 4/27/2018

Said Exceptions have been fixed, code cleaned up a bit,

Update server check will now check HTTP site first, then ping all 12 update servers are report online/offline

Individual server status visible by clicking on DCS Update Server Staus on top right of the status bar)

Cleaning up Individual UI elements and names, since some things have changed under the hood.

Edited April 27, 2018 by SkateZilla

[SkateZilla]

[WineCape]

SkateZilla's Nifty "DCS Updater Utility": To force branches into another directory?

 

SkateZilla's DCS Updater Utility (DCSUU) seems a useful GUI front-end utility to keep updated branches of DCS World apart and to roll back/update certain branches without bothering with exe. command prompts.. - and to run branch builds side by side

 

Here's the question:

I installed DCS just before DCS World 2.5 was released as an "RELEASE BUILD" and installed it under the folder directory E:/Games/DCS World OpenBeta folder

 

Subsequently I updated DCS World to the 2.5.1 (UPDATE/OpenBeta), but I dumped the latter into the SAME E:/Games/DCS World OpenBeta folder, which is not prudent, as I would rather dump all future BETA's into another directory so that SkateZilla DCSUU can be pointed to these separate folders - and keep the RELEASE BUILD separate from in case I need to roll back to a RELEASE BUILD that "works."

 

Anyone here know how to "force-move" the directory structure now, or maybe in the future, so that any OpenBeta future released DCS builds are kept away from the same directory as the RELEASE BUILD, given that all game files (Release and Beta builds) currently are now in a single directory called \....\DCS World OpenBeta\ folder?

 

Do I simply point the DCS Updater utility under the "CUSTOM #1 BUILD fields" - see attached pic - - to the same E:/Games/DCS World OpenBeta folder for now and use that build/original folder structure, for now, as my official release build? And IF so, will the utility itself then create a separate directory (copied?) folder structure, away from the original OpenWorld Beta folder structure? -- See 2nd pic - so that I can run the RELEASE and Beta's side by side, or do I have to do a possibly cut/paste of some folders instead to make this happen?

 

Edited April 28, 2018 by WineCape

[tarball]

it's in extended testing, the new version is a very big step up, the code changes need tested extensively,

 

Just today I found mistakes/conflicts in the detection code and had to revise it a few times to resolve issues.

 

Thank you.

[RogCamp]

Quick Question

 

I have always used your updater to update DCS

I now have DCS 1.5.8.12823 as well as DCS 2.5.1.16543.

 

At this point can I uninstall DCS 1.5.8.12823 using the programs and features page in Control Panel?

 

I think I read somewhere that if you update using the DCS installer it will ask you if you want to uninstall DCS 1.5.

As this does not happen when using your updater I take it it is ok for me to uninstall 1.5 myself at this point.

 

Thanks

[SkateZilla]

Quick Question

 

I have always used your updater to update DCS

I now have DCS 1.5.8.12823 as well as DCS 2.5.1.16543.

 

At this point can I uninstall DCS 1.5.8.12823 using the programs and features page in Control Panel?

 

I think I read somewhere that if you update using the DCS installer it will ask you if you want to uninstall DCS 1.5.

As this does not happen when using your updater I take it it is ok for me to uninstall 1.5 myself at this point.

 

Thanks

 

1.5.8 is now legacy and unsupported, so you can uninstall it by simply deleting the folder,

 

You can use the Add/Remove Programs, but I'm not sure if it will remove 1.5 or 2.5.

[SkateZilla]

Just a Heads up, w/ 2.5 Video Training Module's Are no Longer Supported (Invalid Module).

 

These Video Modules have not Installed Correctly after 1.2.10.32582

 

Next version will disable buttons on Versions 2.0 or Greater.

Edited May 2, 2018 by SkateZilla

[SkateZilla]

SkateZilla's DCS Updater Utility (DCSUU) seems a useful GUI front-end utility to keep updated branches of DCS World apart and to roll back/update certain branches without bothering with exe. command prompts.. - and to run branch builds side by side

 

Here's the question:

I installed DCS just before DCS World 2.5 was released as an "RELEASE BUILD" and installed it under the folder directory E:/Games/DCS World OpenBeta folder

 

Subsequently I updated DCS World to the 2.5.1 (UPDATE/OpenBeta), but I dumped the latter into the SAME E:/Games/DCS World OpenBeta folder, which is not prudent, as I would rather dump all future BETA's into another directory so that SkateZilla DCSUU can be pointed to these separate folders - and keep the RELEASE BUILD separate from in case I need to roll back to a RELEASE BUILD that "works."

 

Anyone here know how to "force-move" the directory structure now, or maybe in the future, so that any OpenBeta future released DCS builds are kept away from the same directory as the RELEASE BUILD, given that all game files (Release and Beta builds) currently are now in a single directory called \....\DCS World OpenBeta\ folder?

 

Do I simply point the DCS Updater utility under the "CUSTOM #1 BUILD fields" - see attached pic - - to the same E:/Games/DCS World OpenBeta folder for now and use that build/original folder structure, for now, as my official release build? And IF so, will the utility itself then create a separate directory (copied?) folder structure, away from the original OpenWorld Beta folder structure? -- See 2nd pic - so that I can run the RELEASE and Beta's side by side, or do I have to do a possibly cut/paste of some folders instead to make this happen?

 

[ATTACH]183418[/ATTACH]

[ATTACH]183420[/ATTACH]

 

They Shouldnt be in the same Folder,

other wise you just updating and switching builds back and forth in a loop, as you are doing it to the same install.

 

if you want Release and Open Beta Separate,

 

Copy/Paste your /DCS World Open Beta/ Folder and Rename it /DCS World/ or /DCS World Release/, Then input it to a Slot in the Utility, Doesnt Matter Which, The Slot Names will be Changed in next public build anyway, and allow for custom names.

 

Select the Release Build, Under Advanced Update options, Choose "Update to the latest Release Version"

 

Which will convert it back to the Release Branch.

 

Leave Open Beta Build in it's own slot, and you can manage them separately.

[0414 Wee Neal]

Can I switch release version to beta and back?

 

HiI have 2.5 release version installed, however my multiplayer server is only operation with beta version. Is there's a way to use the utility to change the release to beta and back easily without me installing a separate beta? My SSD is not big enough to have both on it.

 

 

Thanks

 

 

Neal

[SkateZilla]

HiI have 2.5 release version installed, however my multiplayer server is only operation with beta version. Is there's a way to use the utility to change the release to beta and back easily without me installing a separate beta? My SSD is not big enough to have both on it.

 

 

Thanks

 

 

Neal

 

Adv. Update Options

 

Update to Latest Open Beta Button

-> Changes Branch to Open Beta

-> Updates to Latest Open Beta

 

Update to Latest Release Button

-> Changes Branch to Release

-> Updates to Latest Release Version

[0414 Wee Neal]

Hi SkateZilla

tried the above and worked great, thanks. However I now have an issue with my Rift in that when I start DCS world from the GUI (VR On) the sim starts in the normal VR way with the image on the monitor but no image in the headset, although the head movement works. If I then close the GUI I have the same scenario. I now have to open Occulus GUI (which I have set to run as admin, so I havent been running at the same time as DCS) and it works correctly.

 

I dont know if this is a setting on the GUI or a change with the Beta or something completely unrelated and just coincidence? Have you come across this before?

 

Thanks

 

Neal

[SkateZilla]

Oculus Home used to be able to be Bypassed, I dont think it can anymore.

 

Edit: Just checked, and VR On Button launches to my VR Headset correctly.

 

This might be an Oculus issue, there was a few people that have this problem in the Input/Output -> VR Sub forum.

Edited May 5, 2018 by SkateZilla

[SkateZilla]

I'm still testing the next version.

 

I compiled a new one this morning at 130AM,

 

I've also had some type of Visual Studio Glitch,

All the buttons are now locked (I cant move them, or change their Style/Images etc),

Likely a result of testing the App without the Force XP Style Setting on (This Allows the App to look more modern, and less like Windows XP (Buttons, Drop Downs Etc).

 

So I started replacing them one by one w/ new buttons, and Migrating the code from the old ones to the new ones.

 

I replaced the main buttons, I havent replaced all the module buttons, as I have no plans to move those * YET *,

 

Once I get the buttons back to working correctly and looking correctly, I will make a backup. release, and then begin working on converting to NON XP Style and the new Module Buttons Placement.

 

I will eventually change how the module buttons are presented (size and function), that will be the next code re-write, as well as adding TABS to separate the modules into better categories.

Edited May 5, 2018 by SkateZilla

[WineCape]

Thanks. Worked like a charm your advice earlier!

Keep up the excellent work!

[BlacleyCole]

What language are you using to code this? My question is to see if i would be able to assist you with it if you wanted a test that could do the minor tweaks to help with debugging etc

[SkateZilla]

It's Coded in VB

[tarball]

It's Coded in VB

 

Thanks for your hard work Skatezilla. Is your utility a pass-through to the DCSUpdater command-line tool?

[SkateZilla]

Thanks for your hard work Skatezilla. Is your utility a pass-through to the DCSUpdater command-line tool?

 

Which Tool do you speak of?

[BlacleyCole]

Great I’m very familiar with VKB or was I’ve been out for a few years trying to get back into it

[SkateZilla]

Current Planned Release for the Next version is June 1st, that gives me a few more weeks to test and refine code,

 

Lately while refining I've been re-writing functions one at a time to condense as well as add functions, still the evolution between this version and the current public one is huge.

[BlacleyCole]

Anxiously awaiting its release