You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tested the MRP, and I think it may be related to the strategy of mesh LOD picking, as disabling LOD generation in the import settings seems work right.
Tested versions
v4.3.dev4.official [df78c06]
System information
Godot v4.3.dev4 - Windows 10.0.22000 - Vulkan (Mobile)
Issue description
I just tried applying #79833 in 4.3dev4 to my mobile project and get the following behaviour with a basic imported mesh:
Base and when set to (-1000, -1000, -1000, 2000, 2000, 2000) manually in inspector
![309115736-d0e40aa6-1843-4f1c-a327-83ea9d35e3b7](https://private-user-images.githubusercontent.com/11803603/309126557-ea166f80-d16a-4ed7-856a-4e6866e8c54a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMzk3NjgsIm5iZiI6MTczOTEzOTQ2OCwicGF0aCI6Ii8xMTgwMzYwMy8zMDkxMjY1NTctZWExNjZmODAtZDE2YS00ZWQ3LTg1NmEtNGU2ODY2ZThjNTRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDIyMTc0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZmZDJlNzYxYjAwMTY4ZDE1YWNkOTY5ZmY1Y2QzNjIxYmE0ZmZmODc4N2Q1YzM3ZmUwZWNiMWUzOGNjMmYwZGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.KtimHCHbWDILvhmTI5MVzv5rGk9ke_rtlNlImTYpd5A)
When set in GDScript prior to (or after) adding to the scene with
MM.custom_aabb = AABB(Vector3(-1000, -1000, -1000), Vector3(2000, 2000, 2000))
Steps to reproduce
Load and run the MRP
Toggle comment 'MM.custom_aabb = AABB(Vector3(-1000, -1000, -1000), Vector3(2000, 2000, 2000))' and run again.
Minimal reproduction project (MRP)
MRP_Cubes.zip
The text was updated successfully, but these errors were encountered: