Sorry, I would love to help (I think it's a great map?) however, I do not know teardown modding.

ah i see, well if you were to add it in, just have a warning that says laggy

Tired-Bean 님이 먼저 게시:

ah i see, well if you were to add it in, just have a warning that says laggy

Okay, okay. I'll do that. Maybe tomorrow, or something like that.

HyperPoss 님이 먼저 게시:

Tired-Bean 님이 먼저 게시:

ah i see, well if you were to add it in, just have a warning that says laggy

Okay, okay. I'll do that. Maybe tomorrow, or something like that.

take your time

The reason your bridge is so laggy is the amount of air the raycasts from the camera have to go through to actually hit something to render. You should have the bridge and the catwalk underneath as separate objects still bound together. https://i.imgur.com/7i14ZxK.png the stairs are also extremely inefficient https://i.imgur.com/WXu6EDK.png. Creating a large bounding box full of air.

Doomdrvk 님이 먼저 게시:

The reason your bridge is so laggy is the amount of air the raycasts from the camera have to go through to actually hit something to render. You should have the bridge and the catwalk underneath as separate objects still bound together. https://i.imgur.com/7i14ZxK.png the stairs are also extremely inefficient https://i.imgur.com/WXu6EDK.png. Creating a large bounding box full of air.

Interesting... I'll think about that, and maybe fix it in the next update. Thanks!

Doomdrvk 님이 먼저 게시:

The reason your bridge is so laggy is the amount of air the raycasts from the camera have to go through to actually hit something to render. You should have the bridge and the catwalk underneath as separate objects still bound together. https://i.imgur.com/7i14ZxK.png the stairs are also extremely inefficient https://i.imgur.com/WXu6EDK.png. Creating a large bounding box full of air.

I just noticed that the profiler has the longest delay on "Physics". But... Perhaps it could even be related. It probably also matters that (As long as i remember) each column is a physical body, it’s probably useless especially after I fixed it to the concrete.

HyperPoss 님이 먼저 게시:

Doomdrvk 님이 먼저 게시:

The reason your bridge is so laggy is the amount of air the raycasts from the camera have to go through to actually hit something to render. You should have the bridge and the catwalk underneath as separate objects still bound together. https://i.imgur.com/7i14ZxK.png the stairs are also extremely inefficient https://i.imgur.com/WXu6EDK.png. Creating a large bounding box full of air.

I just noticed that the profiler has the longest delay on "Physics". But... Perhaps it could even be related. It probably also matters that (As long as i remember) each column is a physical body, it’s probably useless especially after I fixed it to the concrete.

Yes it can definitely be related, the weight calculations still have to skip through all the air voxels connecting the object and it has to understand the voxels in that location can pass through.

Let me be clear, "air" and "empty space" are two different things. Voxel objects which are made as one thing with space inbetween will have air voxels fill in that space, those are still accounted for in calculations and still need to continuously skipped through when doing those calculations. Empty space is space in the game which is no where in a shape bounding box.

Any time the rendering system comes comes in contact with this "air" it is fast to skip through unless there is a lot in the direction its going. Weight calculations for physics have to include the air as it checks each voxel and its structure and creates a collision box and maintains proper collision.

So it is fast to skip through the air but when you have thousands to hundreds of thousands of EXTRA voxels to pass through or check it slows down the shape calculations massively in different areas.

Doomdrvk 님이 먼저 게시:

HyperPoss 님이 먼저 게시:

I just noticed that the profiler has the longest delay on "Physics". But... Perhaps it could even be related. It probably also matters that (As long as i remember) each column is a physical body, it’s probably useless especially after I fixed it to the concrete.

Yes it can definitely be related, the weight calculations still have to skip through all the air voxels connecting the object and it has to understand the voxels in that location can pass through.

Let me be clear, "air" and "empty space" are two different things. Voxel objects which are made as one thing with space inbetween will have air voxels fill in that space, those are still accounted for in calculations and still need to continuously skipped through when doing those calculations. Empty space is space in the game which is no where in a shape bounding box.

Any time the rendering system comes comes in contact with this "air" it is fast to skip through unless there is a lot in the direction its going. Weight calculations for physics have to include the air as it checks each voxel and its structure and creates a collision box and maintains proper collision.

So it is fast to skip through the air but when you have thousands to hundreds of thousands of EXTRA voxels to pass through or check it slows down the shape calculations massively in different areas.

Hmm, if so, I'll definitely fix it. Thank you!

Doomdrvk 님이 먼저 게시:

HyperPoss 님이 먼저 게시:

I just noticed that the profiler has the longest delay on "Physics". But... Perhaps it could even be related. It probably also matters that (As long as i remember) each column is a physical body, it’s probably useless especially after I fixed it to the concrete.

Yes it can definitely be related, the weight calculations still have to skip through all the air voxels connecting the object and it has to understand the voxels in that location can pass through.

Let me be clear, "air" and "empty space" are two different things. Voxel objects which are made as one thing with space inbetween will have air voxels fill in that space, those are still accounted for in calculations and still need to continuously skipped through when doing those calculations. Empty space is space in the game which is no where in a shape bounding box.

Any time the rendering system comes comes in contact with this "air" it is fast to skip through unless there is a lot in the direction its going. Weight calculations for physics have to include the air as it checks each voxel and its structure and creates a collision box and maintains proper collision.

So it is fast to skip through the air but when you have thousands to hundreds of thousands of EXTRA voxels to pass through or check it slows down the shape calculations massively in different areas.

It doesn't seem to work. Maybe I did something wrong... But here's another video YouTube Perhaps it's just too big dynamic building.

I'd like to review what you did if you could post another version on the workshop as an unlisted map and link it here I would be happy to review it.

Though after viewing it again and understanding the length of the bridge it is very possible the long bridge is seriously too much

. Also theres a warning about going over 400 meters with the shadow volume as it seems to seriously mess with AMD gpus. What your video showed and my own test showed was that the bridge was the most taxing on the physics aspect.

Doomdrvk 님이 먼저 게시:

I'd like to review what you did if you could post another version on the workshop as an unlisted map and link it here I would be happy to review it.

Though after viewing it again and understanding the length of the bridge it is very possible the long bridge is seriously too much

. Also theres a warning about going over 400 meters with the shadow volume as it seems to seriously mess with AMD gpus. What your video showed and my own test showed was that the bridge was the most taxing on the physics aspect.

Okay, I'll post this for the link so you can try it, as far as I remember it's possible) I'll also try to reduce it by one "Segment" (That's 2 towers). And make some other minor changes. Thanks again.

Doomdrvk 님이 먼저 게시:

I'd like to review what you did if you could post another version on the workshop as an unlisted map and link it here I would be happy to review it.

Though after viewing it again and understanding the length of the bridge it is very possible the long bridge is seriously too much

. Also theres a warning about going over 400 meters with the shadow volume as it seems to seriously mess with AMD gpus. What your video showed and my own test showed was that the bridge was the most taxing on the physics aspect.

Here you go!

Its disappointing but it does just seem Teardown can't handle such a massive million voxel+ physical body.