Post by remussirion on May 8, 2018 15:24:23 GMT -5
Update Update: SOLVED
nowadays, sims4studio can handle the textues without the fix below!
Update: SOLVED
Patching sims4studio to use 4 GB of virtual memory solved the issue for me. No crashes at all anymore. Get the 4GB patch here -> LINK
original post below:
Hey hey,
I'm posting this here instead of the bug report section as I have the impression that it does not apply to everyone and therefore might not be a general issue.
When I'm importing a skin texture that has HQ size (2048x4096 px), S4S (version 3.1.1.5 (wishes) crashes; independetly of how many swatches are in the package already (whether it's 1 or 20, doesn't matter). Most of the times it crashes immediately, sometimes I can import up to 8 swatches without a crash. One of the affected skin files can be found here: LINK. It's just an example as I had this problem with all skin files, even those that had just 6 swatches in total.
In the past, when creating skins, s4s crashed every 4-10 swatches and I made my peace with that, but now it crashes most of the time without me being able to even add one single swatch. The first seconds it looks like normal and is loading, but then the program becomes unresponsive and crashes completely or just keeps loading forever.
Additional background info: I recently switched to windows 10 but I am quite sure that the crashes started later than that. However, there were several windows 10 updates in the meantime. Therefore I reinstalled the graphics card driver. That didn't help though. I also reinstalled S4S and even tested an older version, but that didn't help either.
Two of my friends reported crashes with HQ textures, too (makeup and clothing that aren't as heavy on the package file size as skin textures are).
My computer specs:
CPU: Intel Core i7-920 2.67GHz; RAM: 24 GB; GPU: Nvidia Geforce GTX 960; Windows 10 Pro version 1709 build 16299.402
During import, the RAM usage is at 26-60% (depends on what I'm doing in parallel. Closing EVERY other program does not help the issue though, even if S4S is the only program to use after rebooting the computer); CPU is at 3-10%, raises to 40 while importing and then drops back to ~3% when it crashes.
Windows Event Viewer Logs:
With each crash, 2 entries appear:
Source: .NET Runtime; event ID: 1026; Time: 22:15:58
Source: Application error; event ID: 1000; Time: 22:16:01
Name der fehlerhaften Anwendung: S4Studio.exe, Version: 3.1.1.5, Zeitstempel: 0x5acbe93b
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.16299.402, Zeitstempel: 0x81d25214
Ausnahmecode: 0xe0434352
Fehleroffset: 0x00103f12
ID des fehlerhaften Prozesses: 0xe510
Startzeit der fehlerhaften Anwendung: 0x01d3e7089cf52607
Pfad der fehlerhaften Anwendung: D:\Programme\Sims 4 Studio\S4Studio.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\KERNELBASE.dll
Berichtskennung: 2c960090-b6f7-4b6c-bc14-6935f65a3433
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
The S4S logs don't say anything about a crash though:
[10:10:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.Init[0]] OS: Windows 10 Pro
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing game files...
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing thumbnails...
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing Studio Mods folder...
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Done.
[10:36:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.Init[0]] OS: Windows 10 Pro
[10:36:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing game files...
[10:36:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing thumbnails...
nowadays, sims4studio can handle the textues without the fix below!
Update: SOLVED
Patching sims4studio to use 4 GB of virtual memory solved the issue for me. No crashes at all anymore. Get the 4GB patch here -> LINK
original post below:
Hey hey,
I'm posting this here instead of the bug report section as I have the impression that it does not apply to everyone and therefore might not be a general issue.
When I'm importing a skin texture that has HQ size (2048x4096 px), S4S (version 3.1.1.5 (wishes) crashes; independetly of how many swatches are in the package already (whether it's 1 or 20, doesn't matter). Most of the times it crashes immediately, sometimes I can import up to 8 swatches without a crash. One of the affected skin files can be found here: LINK. It's just an example as I had this problem with all skin files, even those that had just 6 swatches in total.
In the past, when creating skins, s4s crashed every 4-10 swatches and I made my peace with that, but now it crashes most of the time without me being able to even add one single swatch. The first seconds it looks like normal and is loading, but then the program becomes unresponsive and crashes completely or just keeps loading forever.
Additional background info: I recently switched to windows 10 but I am quite sure that the crashes started later than that. However, there were several windows 10 updates in the meantime. Therefore I reinstalled the graphics card driver. That didn't help though. I also reinstalled S4S and even tested an older version, but that didn't help either.
Two of my friends reported crashes with HQ textures, too (makeup and clothing that aren't as heavy on the package file size as skin textures are).
My computer specs:
CPU: Intel Core i7-920 2.67GHz; RAM: 24 GB; GPU: Nvidia Geforce GTX 960; Windows 10 Pro version 1709 build 16299.402
During import, the RAM usage is at 26-60% (depends on what I'm doing in parallel. Closing EVERY other program does not help the issue though, even if S4S is the only program to use after rebooting the computer); CPU is at 3-10%, raises to 40 while importing and then drops back to ~3% when it crashes.
Windows Event Viewer Logs:
With each crash, 2 entries appear:
Source: .NET Runtime; event ID: 1026; Time: 22:15:58
Application: S4Studio.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<channelset>)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)
at System.Windows.Interop.HwndTarget.OnWindowPosChanged(IntPtr)
at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
</channelset>
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<channelset>)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)
at System.Windows.Interop.HwndTarget.OnWindowPosChanged(IntPtr)
at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
</channelset>
Source: Application error; event ID: 1000; Time: 22:16:01
Name der fehlerhaften Anwendung: S4Studio.exe, Version: 3.1.1.5, Zeitstempel: 0x5acbe93b
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.16299.402, Zeitstempel: 0x81d25214
Ausnahmecode: 0xe0434352
Fehleroffset: 0x00103f12
ID des fehlerhaften Prozesses: 0xe510
Startzeit der fehlerhaften Anwendung: 0x01d3e7089cf52607
Pfad der fehlerhaften Anwendung: D:\Programme\Sims 4 Studio\S4Studio.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\KERNELBASE.dll
Berichtskennung: 2c960090-b6f7-4b6c-bc14-6935f65a3433
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
The S4S logs don't say anything about a crash though:
[10:10:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.Init[0]] OS: Windows 10 Pro
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing game files...
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing thumbnails...
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing Studio Mods folder...
[10:10:32] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Done.
[10:36:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.Init[0]] OS: Windows 10 Pro
[10:36:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing game files...
[10:36:31] [v3.1.1.5] Info [S4Studio.Shared.AppModel.DoInit[0]] Initializing thumbnails...