Jump to content

Stabler De-Jank and Game Juice Update (1.17.5 & 1.17.6)


Tyron
 Share

Recommended Posts

Dear Extraordinary Survivalists
v1.17.5, a stable release, can now be downloaded through the account manager.

[Edit:] Also released 1.17.6 to fix a client crash related to condensers and a dupe bug related to wall leaning tools

The final polishing, I hope.

Vintagestory_2022-09-14_15-35-30-26.thumb.jpg.2d361f04c69ed0702d8b46378534154f.jpg
Chiseled room by Andre#3367, shared on discord

Game updates

  • Tweak: Reduced server performance cost for stone-throwing enemies
  • Tweak: Significantly reduced RAM usage caused by missing blocks, e.g. when mods were removed (20 gb -> 7 gb in one test case)
  • Tweak: No longer drop crop harvest in multiple 1x items to prevent lag
  • Fixed: Perishable info missing on placed crocks, bowls and pots
  • Fixed: Blackguards breaking cracked tool vessels got no drops
  • Fixed: Performance: Clay ovens filled with firewood unecessarily redrawing chunks twice a second
  • Fixed: Missing translation entries for fruit tree fruits in meals
  • Fixed: Fruit tree fruit jams hat incorrect satiety values
  • Fixed: Condenser and fruitpress: Placing liquid containers other than buckets were invisible
  • Fixed: Milking ewes consumed 1 litre at the end of the process
  • Fixed: Sometimes able to find 0 copper stacks in ruins
  • Fixed: Bears not able to step on blocks in some cases
  • Fixed: Untranslatable text with placed food containers
  • Fixed: Startup crash for some heavily modded worlds or similar cases
  • Api Fixed: CollectibleObject.OnBeforeRender(), renderInfo.dt set to 0 for not currently held items
  • Api Fixed: tree.MergeTree() was not properly fixed
  • Api Fixed: Decor block sounds were ignored, now always used. Can use attribute block "ignoreSounds:true" to restore old behavior.
  • Api Fixed: Stack overflow when using obsolete method Collectible.GetDurability
  • Api Fixed: Crash on ground storage placement of blocks/items with overlay textures
  • Api Fixed: Might fix "Sold by" handbook entry not working for modded items/blocks

 

 


View full record

  • Like 5
  • Thanks 4
Link to comment
Share on other sites

@Tyron

3.10.2022 23:13:39 [Fatal] Caught unhandled exception in thread 'networkproc'. Exiting game.
3.10.2022 23:13:39 [Fatal] System.NullReferenceException: Object reference not set to an instance of an object.
   at Vintagestory.GameContent.BlockEntityCondenser.genBucketMesh() in C:\Users\Tyron\Documents\vintagestory\game\VSSurvivalMod\BlockEntity\BlockEntityCondenser.cs:line 149
   at Vintagestory.GameContent.BlockEntityCondenser.FromTreeAttributes(ITreeAttribute tree, IWorldAccessor worldForResolving) in C:\Users\Tyron\Documents\vintagestory\game\VSSurvivalMod\BlockEntity\BlockEntityCondenser.cs:line 293
   at Vintagestory.Client.NoObf.ClientChunk.PreLoadBlockEntitiesFromPacket(Packet_BlockEntity[] blockEntities, Int32 blockEntitiesCount, ClientMain game) in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\Model\ClientChunk.cs:line 359
   at Vintagestory.Client.NoObf.ClientWorldMap.LoadChunkFromPacket(Packet_ServerChunk p) in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientWorldMap.cs:line 657
   at Vintagestory.Client.NoObf.SystemNetworkProcess.ProcessInBackground(Packet_Server packet) in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\Systems\NetworkProcess.cs:line 218
   at Vintagestory.Client.NoObf.SystemNetworkProcess.TryReadPacket(Byte[] data, Int32 dataLength) in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\Systems\NetworkProcess.cs:line 152
   at Vintagestory.Client.NoObf.SystemNetworkProcess.NetworkProcess() in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\Systems\NetworkProcess.cs:line 130
   at Vintagestory.Client.NoObf.ClientThread.Update() in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientThread.cs:line 80
   at Vintagestory.Client.NoObf.ClientThread.Process() in C:\Users\Tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientThread.cs:line 34

Oops...

Link to comment
Share on other sites

So the game, installed from scratch, crashes when I try to run it with the packed Volumetric Shaders mod (installed as part of the 1.17.6).
Crashdump : 

Spoiler

Running on 64 bit Windows with 16 GB RAM 
Game Version: v1.17.6 (Stable)
05/10/2022 17:31:30: Critical error occurred in the following mod: volumetricshading@0.5.1
Loaded Mods: volumetricshading@0.5.1, game@1.17.6, creative@1.17.6, survival@1.17.6
Involved Harmony IDs: com.xxmicloxx.vsvolumetricshading
System.TypeLoadException: Could not load type 'Vintagestory.API.Common.Action' from assembly 'VintagestoryAPI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.
   at VolumetricShading.Patch.ShaderPatcher.Reload()
   at VolumetricShading.ShaderRegistryPatches.LoadRegisteredCallsite(Dictionary`2 includes)
   at Vintagestory.Client.NoObf.ShaderRegistry.loadRegisteredShaderPrograms_Patch0()
   at Vintagestory.Client.NoObf.ShaderAPI.ReloadShaders() in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\API\ShaderAPI.cs:line 54
   at Vintagestory.Client.NoObf.ClientMain.ProcessServerReady() in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientMain.cs:line 1923
   at Vintagestory.Client.NoObf.ClientMain.ExecuteMainThreadTasks(Single deltaTime) in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientMain.cs:line 1139
   at Vintagestory.Client.GuiScreenConnectingToServer.RenderToDefaultFramebuffer(Single dt) in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\MainMenu\Screens\GuiScreenConnectingToServer.cs:line 381
   at Vintagestory.Client.ScreenManager.Render(Single dt) in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\ScreenManager.cs:line 711
   at Vintagestory.Client.ScreenManager.OnNewFrame(Single dt) in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\ScreenManager.cs:line 615
   at Vintagestory.Client.NoObf.ClientPlatformWindows.window_RenderFrame(Object sender, FrameEventArgs e) in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientPlatform\GameWindow.cs:line 131
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at OpenTK.GameWindow.RaiseRenderFrame(Double elapsed, Double& timestamp) in C:\Users\Nexrem\Desktop\transfer\opentk\src\OpenTK\GameWindow.cs:line 479
   at OpenTK.GameWindow.DispatchRenderFrame() in C:\Users\Nexrem\Desktop\transfer\opentk\src\OpenTK\GameWindow.cs:line 454
   at OpenTK.GameWindow.Run(Double updates_per_second, Double frames_per_second) in C:\Users\Nexrem\Desktop\transfer\opentk\src\OpenTK\GameWindow.cs:line 375
   at Vintagestory.Client.ClientProgram.Start(ClientProgramArgs args, String[] rawArgs)
   at Vintagestory.ClientNative.CrashReporter.Start(ThreadStart start) in C:\Users\tyron\Documents\vintagestory\game\VintagestoryLib\Client\ClientPlatform\ClientNative\CrashReporter.cs:line 93
 

 

Link to comment
Share on other sites

@Philippe J Mods are unsupported additions and are up to each player's individual responsibility. Please do not expect the dev team to fix your mod problems.

Instead, go to the mod author with the crash. There you will most likely be told "of course it crashes, I haven't updated it yet" or something to that effect. But, in the incredibly unlikely case that there is something fundamentally broken in the modding API that prevents Volumetric Shading from working entirely on this version, and the mod author is unable to fix it themselves, then the mod author will carry that problem to the VS dev team.

Link to comment
Share on other sites

My apologies, it appears I installed the mod a long time ago (a year or two) on my machine and it persisted despite me doing a clean install of Vintage Story today. It had been a long time using this machine to play VS, so I foolishly thought this came with the setup !
Sorry for the confusion ! 😔

Edited by Philippe J
Link to comment
Share on other sites

Don't worry, hope you run now game smoothly :)

I have a hud clock and version .0.2.7 crash VS 1.17+ everytime try tu run. And I was confused why it happens. After update to 0.2.8 all runs great! So sometimes mod makes your life harder. 

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.