same here. It’s painless. But then, I hardly ever feel the need to. The versions are pretty close, and often the beta has some sweet new gubbins the release lacks.
Changelog for v8.02.2019.1 / 1.1.0.1024:
-Condensed Functions Code
-Rewritten Module Scanning Code
-SRS Added to External Applications List
-Adjusted A-4EC and MB-339 Links
-Process Management Cleaning, Setting up for a new process management system.
-Added Fw-190 A8 Assets
-Added F/A-18C Aggressors Campaign Assets
-Added Jagdflieger Campaign Assets
The Process Tracking / Multiple Launch Modes Haven’t Been integrated yet,
I am going to further Condense some functions code before I add new functions.
Added to First Post of EDForum Thread and Updater.
9 Likes
Changelog for 08.05.2019.1 / 1.1.0.1025:
-Adjusted Modelviewer2 / QtPLugin Detection (Will check versions of QtPlugin and Update)
-Adjusted Scanning
-Added “Delete Pre-Compiled Shaders” Option under Adv. Update Options
(Note: Saved Games folder for build must be set)
-Fixed Mis-Link in Launch SRS External Applications Function
7 Likes
Nice! I didn’t know I wanted that feature, but I really do!
3 Likes
Agreed!
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.Process.Kill()
at SZGSUPDATER.Form1.CheckProcess()
at SZGSUPDATER.Form1.Form1_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3815.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
SZGS Mini Updater
Assembly Version: 1.0.0.1002
Win32 Version: 1.0.0.0
CodeBase: file:///H:/DCS%20World/SZGS%20Mini%20Updater.exe
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3801.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3815.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3815.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Can’t update. The above exception was thrown when running the thing as admin. It also still sometimes randomly sets its screen position to -32000, -32000. I fix this by going to /appdata/ and editing the .cfg but its a pain.
There should be a Restore option in the system tray right click menu that sets position to 100, 100 and restores window.
I purposely set my location to the -32000,-32000 and tested the function and it restored the window.
I will likely add a fail safe, to reset location to 15,15 if the location exceeds a specific value.
I havent pinpointed why it saves as -32000 yet, but a few other people on VB Foums have similar issues.
The Error Posted above is also a rare occurance, and is when the Process being closed is locked via permissions or user settings.
I hope to re-vamp the update procedure w/ a new one, I am trying to keep everything in a single EXE file, but eventually I will have to start including Libraries and Separate EXE’s for other functions.
3 Likes
Cool. I redownloaded the .exe and overwrote the old one with it, works fine. So that’s sorted. I never saw that restore option. Neat!
Big ups and kudos for the clean shaders button. It will get used at least once a forthnight.
1 Like
Im having a few problems with launching this tonight. as soon as i click on it to load up DCS i get the “has stopped working” message
anyone else having trouble or is it just me? on a side note i am having issues with BMS tonight as well so its most likely my pc throwing a fit but just thought id ask
Yup. I see this too. It stays minimized and does not open.
one of the windows updates / nvidia updates was causing a problem iirc w/ alot of applications.
1 Like
edit: double post.
in the system tray, right click the Updater Icon and choose restore window.
Pending Changelog:
-Added F-16C Module Assets
-Added Worlds Apart Campaign Assets
-Adjusted code for SRS Path saving
-Adjusted Tool Tips for several items
-Adjusted code for some launch routines
-Added checkbox for Oculus Mirror to Enable Mirror w/ “Broadcasting / Streaming” Settings.
It will override any set settings for Oculus Mirror with settings below recommended by Oculus, I will play with it a little bit to optimize size etc
–Size 1280 1280
–FovTanAngleMultiplier 1.3 1.3
–DisableTimewarp
–SymmetricFov
–RightEyeOnly
–DisableFovStencil
–IncludeSystemGui
–IncludeNotifications
Right now I’m still working on some code changes,
And I also Need to re-write the version numbers fetching code and look for a new update process.
As of Right now:
App Update Check, Updating via app, DCS Server Check, Version Numbers Fetching etc are now disabled.
Seems someone reported my App to my Webhost as malicious and they locked my account and they will not unlock it.
So to avoid this issue I’m removing references to external files from the app.
This means i have to re-code how the version number fetcher works, if I can simply pull text from a google drive file I would, and I also dont want to parse the update.DCS Website Directly to retrieve them.
Same for App Version/Update Check, and the files associated.
I will just have users come to the forum to download latest versions again.
3 Likes
Is this still the best utility to use to go from stable to open? I just bought the jf17 and dont really want to run to installs.
1 Like
It is a great utility that i use every day , primarily for VR (flying) and pancake (administrative and mission creation) modes , and the occasional reversion/version changes as well . . I cannot imagine anyone flying DCS not using it . Two clicks (3 at most) to do whatever you wish , is much quicker/simpler than the command line method , even for those expert in its usage . I heard one guy say he didn’t want another program running , but i simply close it as soon as i see the “logging in” box .
Thanks for the post !
2 Likes
Yes ! But be advised open is a mess right now…
Absolutely. This tool is very good.
Thanks guys!
Describe mess…
I’ll start by saying that it is bad enough that ED has not pushed it into the stable version for 4 months . Prolly a record-certainly so for the three years i’ve been flying it .
For details visit Ed Forums>2.5>Bugs and problems
To summarise , buggy and VERY poor performance , particularly in VR or multiplayer , broken user missions/campaigns and essential third-party mods such as Vaicom Pro . I finally got the latter to work again , but gave up on open beta after 2-1/2 months (for the first time !) Reverted to stable and broke Vaicom again . (Sigh)
1 Like