PC Falling through the landscape since last update

[geotavros]

People started to report that they are falling through the landscape on my map KF-IceArena since last update http://steamcommunity.com/sharedfile.../?id=642421282

I tried it myself in local game and wasn't falling through floor until wave 5. I was running from zeds and fell through the floor and died. Couldn't reproduce it.
In another local game the boss(fat one) died during mid fight. I wasn't looking at him, was running away, but he had half of his HP and died instantly. I assume he fell through the floor too.

Do I need to recompile the map or is it a game bug?

 

[geotavros]

This reproduces well on wave 5. Both zeds and players start to fall through landscape at random locations

 

[slayer123]

This happened on the map water on Mars everyone randomly fell through the floor at different times and at different points, I saw various zeds also fall through the floor.Never had this problem before the update.

 

[NED79]

Happening on Afghanistan as well.

 

[pokerman123]

The major common points between IceArena and WaterOnMars, their grounds are all made of "Landscape".

Therefore I am pretty sure they screwed up Landscape in this version and cause all the maps using Landscape to be unplayable for everyone.

This is a critical global bug.

 

[[TW]Swag]

Thank you for the heads up. We are looking into it.

If an author of a map that is having the issue is willing to provide me an uncooked version of the map to look at, I'd greatly appreciate it. Speeds up reproduction.

 

[pokerman123]

Welp, not only Landscape caused bug.

The map "KF-MinecraftTest_B7_Fix" , player will fall out of map too, but this map doesn't use any landscape, the ground is made of "StaticMesh".

I still not know what really cause it but this problem happened after Summer Sideshow update.

 

[pokerman123]

I figure out something more, these lands are showing "dark-red" in Rigid-Body view.

The Dark-red in rigid body view indicate that surface use "realistic collision", not "simple box collision".

Simple box collision meshes will showing Cyan in rigid body view.

Therefore the Dark-red surfaces is bugged in this version.

 

[pokerman123]

Although the landscape will not rendering in Rigid Body view, but I am pretty sure it use the "Complex collision" too as the "Darkred" surfaces.

I think the "Complex Collision" is bugged in this version.

You better focus the codes of complex collision in the game engine.



ScreenShots

BUG map - WaterOnMars , the landscape will not rendering, but its not simple box collision (which will rendering cyan).

BUG Map - IceArena , same as WaterOnMars, the ground isn't rendering Cyan in Rigid Body View.

BUG Map - MinecraftTest_B7_Fix

This time the ground is made of StaticMeshes, but it use complex collision too (Which is rendering Dark Red)

Not A Bug Map - Defend_Thyself

This map's ground look like landscape, but it actually is StaticMeshes, and it rendering Cyan in Rigid Body View.
Therefore the ground is using "Simple Box Collision", this map doesn't have any falling bug.

 

[[TW]Swag]

Fantastic explanations of the problem. Can I please get an uncooked version link sent to me via DM so that we can look at the problem directly?

 

[pokerman123]

I don't know how to make map uncooked, also I am not the mapper of maps above.

 

[geotavros]

Surprisingly I didn't get any notifications on email about posts in my thread... Only for the first reply after which I visited the forum.

Not sure I have the uncooked version of my map, didn't even know it is necessary to keep it. Does the uncooked version store some valuable information?

I have some older versions of my map, but how do I find out whether they are uncooked?

 

[[TW]HyperSniper]

We think we found what may have caused this, and we will be looking into it further to remedy the problem!

 

[geotavros]

I've probably found a workaround for this issue. In the Landscape Editor tool
- go into Landscape Info
- Change Section Size to 31(was 255)
- Set Sections per Component to 1
- Choose "Expand". Note: was Crop, but I noticed some artifacts with Crop being used.
- Click 'Change Component Size'

 

[NED79]

HyperSniper;n2299024]We think we found what may have caused this, and we will be looking into it further to remedy the problem!

Thanks!

 

[geotavros]

Looks like "Crop" in my workaround leads to some issues with default material being used on some parts of the landscape. Or idk... Anyway I used the "Expand" option and was able to fix the default material in some parts of the landscape

 

[®omano]

Why do you try to find workaround, when they said they surely found the reason and will so surely fix it soon?