V2.5 b32 Hotfix

cheebsco

cheebsco

Fun Pimps Staff
old_2_5_b32_hotfixHeader.jpg

Howdy survivors!

We're pushing another hotfix to Stable today with V2.5 b32. This update focuses on vehicle improvements, improved gear, and several outfit fixes.

The big news is a simplified vehicle camera method that should eliminate the stuttering many of you experienced with variable frame rates. While passengers may still notice some reduced jitter, this is a significant improvement for drivers. We're continuing to work on further refinements.

We've also improved the male and female rogue hood with variants for those of you who prefer a more tactical approach to the apocalypse. Several cosmetic fixes round out this update, including fixes for the pirate outfit, raider outfit warnings, and lumberjack gloves.

Here's what made it into V2.5 b32:

Changed

  • Updated pirate male gearset
  • Updated eyepatch skinning with adjusted mesh

Fixed

  • Hinge Joint warnings in first person view gear
  • Male and female rogue gear
  • Warning thrown when wearing raider outfit (Added missing connected body for CrotchArmor's HingeJoint)
  • Vehicle camera stuttering caused by variable frame rates and hitching (Note: Passengers may still experience some jitter - we are actively working on further improvements)
  • Twitch Hypetrain v1 deprecation
  • Dismemberment shader not displaying correctly when entity is being shocked
  • Lumberjack Gloves were invisible in first person view for female characters
 
VenomGoo said:
What about this flickering with the lighting while just walking around? Any chance of that getting a fix?
Click to expand...
Flickering with lighting may be related to your antialiasing settings. Try different settings and see if it helps. I don't have any flickering on PC. Not sure if you're on console or not.
 
n2n1 said:
I'm waiting for the correction of the non-rendering of water chunks...
Is there any hope for v2.6?
https://community.thefunpimps.com/t...-near-water-and-missing-water-textures.46169/
Click to expand...
I suppose that depends on how much time is needed to find the cause. That thread points out that they are aware of the problem and have a ticket for it, so they should be working on it. My guess is that it'll either be in another 2.5 update or else in 2.6. I doubt it will take longer than that, but that's just my guess.
 
You must log in or register to reply here.
Back
Top