v21.02.05 Discussion Thread
-
Glad you're finding the forums beneficial. Hopefully, we'll be able to identify and resolve issues quicker this way.
We need an Application Error & corresponding .Net runtime Error as a pair.
The 2nd entry (11:23:48 .Net runtime Error) should have the additional detail needed.
-
@sim-plicity-dev said in v21.02.05 Discussion Thread:
Glad you're finding the forums beneficial. Hopefully, we'll be able to identify and resolve issues quicker this way.
We need an Application Error & corresponding .Net runtime Error as a pair.
The 2nd entry (11:23:48 .Net runtime Error) should have the additional detail needed.
Log Name: Application
Source: .NET Runtime
Date: 17/08/2021 11:23:46
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Intel8700K
Description:
Application: SW25.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Compact.frmMain..ctor(System.String[])
at Compact.Program.Main(System.String[])Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-08-17T09:23:46.4322556Z" />
<EventRecordID>122191</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Intel8700K</Computer>
<Security />
</System>
<EventData>
<Data>Application: SW25.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Compact.frmMain..ctor(System.String[])
at Compact.Program.Main(System.String[])</Data>
</EventData>
</Event> -
It appears your Windows user account privileges were insufficient to correctly install the required dlls during the installation.
I'll send you a zip file with the missing dlls which you'll need to extract to your "C:\Program Files\Sim-plicity\SW25" folder.
-
@sim-plicity-dev said in v21.02.05 Discussion Thread:
It appears your Windows user account privileges were insufficient to correctly install the required dlls during the installation.
I'll send you a zip file with the missing dlls which you'll need to extract to your "C:\Program Files\Sim-plicity\SW25" folder.
awesome.
Thanks
-
-
Did you by any chance uninstall & reinstall the Base Driver package?
Can you attempt to launch SW25.exe then repeat the "Event Viewer" operation, this time reducing the "Logged" value to "Last Hour"?
-
@mr_dino can you explain how you feel the differenfce?
-
@sim-plicity-dev once these updates are avaible again are they also for the sw15 wheelbase?
Regards, Max -
@sim-plicity-dev said in v21.02.05 Discussion Thread:
Did you by any chance uninstall & reinstall the Base Driver package?
Can you attempt to launch SW25.exe then repeat the "Event Viewer" operation, this time reducing the "Logged" value to "Last Hour"?
Base driver packaged solved the issue.
Thanks -
As all SW15 wheelbases shipped with v21.02.05 firmware, there's nothing new in this release. Future releases will include SW15 updates.
-
@frijsdijk stronger low and mid range torque, wheel is more reactive, it's hard to explain just feels a lot better. The extra speed helps too.
-
Little issue I found, profile is not saving changes to virtual torque so I have to set it every time I turn the base on.
-
i have a SW25, i still have V19.08.05 firmware, looking forward to a safe update.
-
@tim_haynes88 same here with my SW20v3 and on 19 08 06.
-
@tim_haynes88 more than safe update it seems to be a safe way to do the update. Lets see...
-
@mr_dino said in v21.02.05 Discussion Thread:
Little issue I found, profile is not saving changes to virtual torque so I have to set it every time I turn the base on.
Many thanks, this has been logged as an issue and will be fixed in v21.02.06
-
We've had @Wes1987's unit back and identified the cause of the update issues.
v21.02.05 uses a new update mechanism designed to eliminate reported intermittent failures with the old updater. Unfortunately, it appears to have broken the failsafe bootloading mechanism that ensures an unsuccessful update can be easily recovered.
We will revert to the old update mechanism for v21.02.06 and look to resolve the updater issue in v21.07.01
-
@sim-plicity-dev I have been watching this as I have been reluctant to update my older 7C+ with the new firmware. While you have found the issue still not certain if it is worth the update or wait for the new version. Any recomendations?
-
@sim-plicity-dev That's great news, thankfully you managed to catch this before more devices were updated. Looking forward to getting it back in my hands so I can get back on the track.
-
v21.02.05 is now classed as "Do Not Install" for all.
v21.02.06 will incorporate fixes but is still "alpha" software and will likely change a few more times on its way to "Stable"
We decided on the staged releases as our in-house testing cannot replicate the myriad of available environments and we do need validation that changes in each release do not affect stability outside our "lab environments".
As all new versions will start out as Alpha regardless of feature set, the decision is more at which stage you feel comfortable to switch from your existing version.
At this point the key differentiator between v21.02.06 & v21.07.01 will be the firmware delivery mechanism (updater), with v21.02.06 reverting to the mechanism that has been in use (with minor niggles) since 2018 while v21.07.01's mechanism will look to resolve both those niggles & the issues discovered in v21.02.05.
