Wrye Bash - All Games

[Supierce]

With UFO4P's default Delev tag, Wrye Bash's bashed patch reverts about half of UFO4P 2.0.3 beta's leveled item lists to their vanilla state. I'm not sure why this happens since those records don't conflict with anything. With the addition of a Relev tag, the bashed patch leaves UFO4P's changes in place. I'm using the current WIP, but I suspect the same thing happens with DEV.

I'm posting this in both forums. Let me know if you need more information. Thanks!

[Beermotor]

7 hours ago, Utumno said:

Resizing the icons was hacked in - I don't think that the dat files have anything to do - they are not written anyway when icon size changes. I think this is a bug in the ancient wx version we use that will probably go away once we update to newer wx. Meanwhile if anyone can debug this in MS Visual studio please do

It took me forever to trigger a crash, but I managed to do it twice. Same exact unhandled exception each time. I had VS2017 loaded so I punched the debug button..

I apologize because I totally suck at debugging with VS but I got at least a little useful information.

Spoiler

'pythonw.exe' (Win32): Loaded 'C:\Python27\pythonw.exe'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9317_none_508dca76bcbcfe81\msvcr90.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\python27.dll'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\win32u.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32full.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcp_win.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ucrtbase.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shell32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\SHCore.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\combase.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\windows.storage.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shlwapi.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel.appcore.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\powrprof.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\profapi.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\DLLs\bz2.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Python27\DLLs\_hashlib.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptsp.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rsaenh.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcrypt.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\_scandir.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\DLLs\_ctypes.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleaut32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\_core_.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\wxbase28uh_net_vc.dll'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\wxmsw28uh_adv_vc.dll'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\wxbase28uh_vc.dll'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\wxmsw28uh_core_vc.dll'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wsock32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmm.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9317_none_508dca76bcbcfe81\msvcp90.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmmbase.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\comdlg32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.192_none_5d760485a7e0eb41\comctl32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.16299.192_none_8e60f76b0273650f\GdiPlus.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winspool.drv'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\IPHLPAPI.DLL'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\_gdi_.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\_windows_.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\wxmsw28uh_html_vc.dll'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\_controls_.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\_misc_.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\win32\win32gui.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.192_none_d02ca7595f31d9e4\comctl32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\pywintypes27.dll'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msimg32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\win32\win32api.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\version.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\secur32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\win32\_win32sysloader.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\pythoncom27.dll'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\uxtheme.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\urlmon.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imagehlp.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\iertutil.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\win32comext\shell\shell.pyd'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\atl.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'D:\Games\Steam\SteamApps\common\Skyrim Special Edition\Mopy\loot_api.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcp140.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\vcruntime140.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'D:\Games\Steam\SteamApps\common\Skyrim Special Edition\Mopy\loot_api.dll'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winhttp.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\clbcatq.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cldapi.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\aepic.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\fltLib.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntmarta.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\propsys.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Windows.StateRepositoryPS.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mssprxy.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\coml2.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\linkinfo.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntshrui.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\srvcli.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cscapi.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dui70.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\duser.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\chartv.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\OneCoreUAPCommonProxyStub.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dwmapi.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleacc.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\atlthunk.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\TextInputFramework.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\CoreMessaging.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\CoreUIComponents.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\WinTypes.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wtsapi32.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winsta.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\apphelp.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\WindowsCodecs.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Users\beermotor\AppData\Local\Microsoft\OneDrive\17.3.7294.0108\FileSyncShell.dll'. Cannot find or open the PDB file.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wininet.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\networkexplorer.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\_wizard.pyd'. Module was built without symbols.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sxs.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wshom.ocx'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mpr.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\scrrun.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\DataExchange.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dcomp.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d11.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dxgi.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\twinapi.appcore.dll'. Symbols loaded.
'pythonw.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rmclient.dll'. Symbols loaded.
The thread 0x14004 has exited with code 0 (0x0).
Unhandled exception at 0x77C0CFD6 (ntdll.dll) in pythonw.exe: 0xC000041D: An unhandled exception was encountered during a user callback.

 

Like I said,  this isn't gdb so I'm started out pretty lost trying to attach to a running process. Here's a screenshot of the call stack:

Spoiler

The DLL wxbase28uh_vc.dll is part of wxPython 2.8.

So since I'm me and not satisfied with that info,  I loaded Wrye Bash up in VS2017 to step through execution. Once I got to the main window and everything initialized, I clicked to change the icon size and triggered several errors:

Spoiler

pywintypes.error
  Message=(2, 'GetFileVersionInfo:GetFileVersionInfoSize', 'The system cannot find the file specified.')
  StackTrace:
bash\env.py:341 in get_file_version

(Step)
pywintypes.error
  Message=(1812, 'GetFileVersionInfo:GetFileVersionInfoSize', 'The specified image file did not contain a resource section.')
  StackTrace:
bash\env.py:341 in get_file_version
(Step...error repeated ~14 times, which is about the number of icons I have on my bottom bar, not counting the icons from shorcuts in \Mopy\apps\)

 

That section of code in env.py may be completely unrelated and the number of errors equaling the number of icons may be completely coincidental but it's curious indeed.

I apologize for the paucity of information here, but I figured since I was finally able to reproduce the crash I'd take advantage of the situation and get at least SOME info. I hope it is helpful.

[lmstearn]

What on earth does it want the file version of an ico file for?

Looks like they don't have any.

[alt3rn1ty]

23 hours ago, Supierce said:

With UFO4P's default Delev tag, Wrye Bash's bashed patch reverts about half of UFO4P 2.0.3 beta's leveled item lists to their vanilla state. I'm not sure why this happens since those records don't conflict with anything. With the addition of a Relev tag, the bashed patch leaves UFO4P's changes in place. I'm using the current WIP, but I suspect the same thing happens with DEV.

I'm posting this in both forums. Let me know if you need more information. Thanks!

There is also a couple of reports on Unofficial Oblivion Patch comments reference Wrye Bash not doing things as expected ..

Carlos on the Oblivion Wrye Bash nexus comments posted this and a reference link to UOP comments :

Quote

Lubronsbrons may have discovered a bug in how bash tags work - it has been discussed on UOP thread: https://forums.nexusmods.com/index.php?/topic/22693-unofficial-oblivion-patch/page-203#entry56878851

So I'll try to sum it up:
1. UOP adds ACBS tag so that Bashed Patch should import NPC stats correctly
2. However, when a mod A is loaded after UOP, and mod A does have ACBS tag too, the changes from UOP to NPCs "wins".
Example mod: https://www.nexusmods.com/oblivion/mods/33804 
Specifically the No Low Level Processing flag that UOP has switched on for some NPCs on Arena "wins" while a later loaded mod's NLLP flag swiched off should "win".

This may potentially affect many mods out there

Unfortunately I believe Lubronsbrons is using Wrye Bash 306 still for Oblivion, so its a report based on that version in use, I dont know if the quoted problem is reproducible with 307.beta2

.. I have asked Carlos if he can repro the issue on Oblivion Wrye Bash comments with 307.beta2, but I think he was just passing info along.

[Arthmoor]

That behavior wasn't broken back in the day so it must have regressed at some point prior to 306. Mods like TIE that rely heavily on ACBS behavior are going to end up broken if this is not working. I'll see if I can spare some time to check that on my own install.

[Beermotor]

21 hours ago, lmstearn said:

What on earth does it want the file version of an ico file for?

Looks like they don't have any.

Yeah I'm scratching my head too, but I think that error may be an inadvertent red herring from the debugger, complaining about not finding .res files for the icons or something. Like I said Win32 API debugging is like Etruscan to me.

EDIT: just for grins I converted all of the .PNG files to .ICO files, modified the Bash source, and launched. Everything worked but it didn't resolve the crashing issue. 

Another idea might be to to use this resource DLL I compiled with all of the Wrye Bash icons in it.  I'm mostly kidding since I just slapped it together, but it's an idea.

Spoiler

 

[alt3rn1ty]

@Utumno 7-Zip needs attention, apparently it has a couple of bad vulnerabilities so needs updating

New Stable version released v18.01 at 7-Zip org

[Utumno]

Anyone can do that on clean commit on a branch over dev ? See last time this was done - and note things broke - we must keep an eye open

[godescalcus]

A user in a forum mentioned the bashed patch being reported by an SSEEdit form version check script as being version 43. As I don't have that issue, my take would be that the cause is using the old version 307beta1 still available at nexus under old files. Can this be confirmed? Should using the beta2 from nexus or the later version linked in the second post of this thread fix this? Or can the bashed patch version issue be inherited from merging unconverted version 43 esps?

DarkladyLexy, I installed 'Timing is Everything' and when I ran the SSEEdit (Check old form version) script against my entire Guide Build (and not just against the TiE mod), the Bashed Patch was tagged as using Form 43.

 

 

I did some searching and found this discussion on the Wrye Bash GitHub page: Add Form Version to class ModReader: #342

[zimou13]

Although 30 to 60 worldspaces is probably too conservative. A single quest can easily involve 5 worldspace edits, we’re probably talking about hundreds of cells.

see : https://9apps.ooo/

https://vidmate.vip/

https://getmobdro.com/

[Beermotor]

On 2/1/2018 at 9:43 AM, Utumno said:

Anyone can do that on clean commit on a branch over dev ? See last time this was done - and note things broke - we must keep an eye open

I can give it a shot although I'll have to try in a Windows VM. My Python 3 set up is fubar right now.

On 2/2/2018 at 5:37 AM, godescalcus said:

A user in a forum mentioned the bashed patch being reported by an SSEEdit form version check script as being version 43. As I don't have that issue, my take would be that the cause is using the old version 307beta1 still available at nexus under old files. Can this be confirmed? Should using the beta2 from nexus or the later version linked in the second post of this thread fix this? Or can the bashed patch version issue be inherited from merging unconverted version 43 esps?

DarkladyLexy, I installed 'Timing is Everything' and when I ran the SSEEdit (Check old form version) script against my entire Guide Build (and not just against the TiE mod), the Bashed Patch was tagged as using Form 43.

DarkladyLexy is either using Beta1 where the bashed patch had form version 0 which triggered that script or her Bashed Patch isn't getting rebuilt. My recommendation after verifying she's running Beta 2 would be to get her to do a clean rebuild (meaning remove/rename the old file) of her Bashed Patch.

[Beermotor]

On 2/1/2018 at 9:43 AM, Utumno said:

Anyone can do that on clean commit on a branch over dev ? See last time this was done - and note things broke - we must keep an eye open

Done. Pushed branch 'beermotorwb-7zip-update'.  Used the 32-bit 7Zip 18.01 release. I tested unpacking 7z, zip, and rar packages and packed a few projects just to put it through it's paces.

I didn't encounter any issues but it should probably get a second pass by someone on another machine.

 

[Utumno]

Thanks @Beermotor - will have a look and include in my next packaged build - meanwhile what you say everybody - should we include the new installer menu by @Beermotor ? I would take the opportunity to add help to remaining menu items by the way (hint hint)

[Joat_Mon]

2 hours ago, Beermotor said:

I didn't encounter any issues but it should probably get a second pass by someone on another machine.

I tried it out, unpacked SRO, seemed to go okay, took ~7 minutes. When I tried to repack I got an error (see attached screen shot).

 

Trying to pack SRO again now without restarting WB, it is taking a long time but Process Explorer shows me that it is "doing it's thing". I will let it run for awhile and let you know what happens.

Update: It did finish packing after ~40 minutes.

[alt3rn1ty]

5 hours ago, Utumno said:

 - meanwhile what you say everybody - should we include the new installer menu by @Beermotor ?

I still run without Python, so have not tried it, but from what I have seen of the outlined ideas (discussed back at this post forwards) it looks good.

[Supierce]

5 hours ago, Utumno said:

Thanks @Beermotor - will have a look and include in my next packaged build - meanwhile what you say everybody - should we include the new installer menu by @Beermotor ? I would take the opportunity to add help to remaining menu items by the way (hint hint)

I say yes, and thank you! I also tried his 7zip build and didn't have any errors.

[Leonardo]

After I finished my update and cleaned my mod xEdit I rebuilt the bashed patch, I came to think about a version number for a mod to be listed in brackets [version] in the summary of the bashed patch.

What do I need to do in order to add a version number for my mod (a bashtag?) when viewing the summary of the bashed patch?

Also, thanks for the recent WB update.

[alt3rn1ty]

12 hours ago, Leonardo said:

After I finished my update and cleaned my mod xEdit I rebuilt the bashed patch, I came to think about a version number for a mod to be listed in brackets [version] in the summary of the bashed patch.

What do I need to do in order to add a version number for my mod (a bashtag?) when viewing the summary of the bashed patch?

I think that is normally done via the CK, File Menu, Data, then on the data dialogue click Details <- Not sure, never used it, but I think this is where a file version gets set that Wrye Bash notes in the top right hand corner of the Plugin Details panels ..

https://www.creationkit.com/index.php?title=File_Menu#Data

.. Or, I have seen where mod authors have just used the Wrye Bash Plugin Details panel, click in the Description box somewhere and type Version: <number> and then you will notice the Save button becomes unghosted, click it to save the new plugin Header Description

http://wrye-bash.github.io/docs/Wrye Bash Advanced Readme.html#mods-details

[Leonardo]

Oh that, I know how to change the version number in either WMSA or in WBSA.  Also, I just checked in xEdit and my mod had 1.7, which is not correct.  So how do I change that in let say xEdit?

[Supierce]

6 hours ago, Leonardo said:

Oh that, I know how to change the version number in either WMSA or in WBSA.  Also, I just checked in xEdit and my mod had 1.7, which is not correct.  So how do I change that in let say xEdit?

It's in the mod's File Header record - the top record of each esm and esp.

[zilav]

7 hours ago, Leonardo said:

Oh that, I know how to change the version number in either WMSA or in WBSA.  Also, I just checked in xEdit and my mod had 1.7, which is not correct.  So how do I change that in let say xEdit?

You should never change version in the header. This is not a version of your mod, this is a version of the game this plugin is for aka how data is stored inside of it.

[alt3rn1ty]

Here's how the Unofficial Patch Project does it ..

[Leonardo]

15 hours ago, Supierce said:

It's in the mod's File Header record - the top record of each esm and esp.

8 hours ago, zilav said:

You should never change version in the header. This is not a version of your mod, this is a version of the game this plugin is for aka how data is stored inside of it.

I checked that in WB last night and I couldn't change that.

5 hours ago, alt3rn1ty said:

Here's how the Unofficial Patch Project does it ..

 

  Reveal hidden contents

 

 

 

This is what I wanted to know about how to change the version for my mod.  Thanks alt.

[Supierce]

I hate to contradict Zilav, but Leo's question was how to do it in xEdit. That same mod description is part of the File Header and is editable with no more danger than doing it in WB. Just Look for SNAM - Description.   

[Arthmoor]

Yes, that's true, but Zilav was referring to the part of the image alt took where it says v1.70 at the top right. That's what he's saying you should never edit because it'll result in a corrupted plugin. Wrye Bash doesn't let you touch that, but xEdit being what it is, that field is exposed for editing.

@zilav Maybe a good idea to disable editing of that field since there's never a reason to allow it?