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
Qodot's racked up a lot of bugs of late. I'd like to round up the biggest offending bugs in this discussion.
If you have any experience with these bugs, or want to quickly test your setup for these bugs, that'd be greatly appreciated. Don't forget to double check if you're using the latest Github repo version of Qodot, since that's what we're testing right now.
Let's begin:
Being worked on already
#42 I just pushed a fix to resolve "build def text" on config export. Help me test this out! It's live on the master branch right now.
Still broken and waiting for someone to take it
#33 Is broken geometry still an issue for people using skip brushes? Yes see issue for more details. Skip texture behaviour is currently incorrect and I'll need help evaluating how to fix it ;;
#13 Do solid classes still have grossly inaccurate vertices? Or can people build them without issue? Yes this is still a known issue as reported by a few users.
Solved
#46Let me know if your CharacterBody3D nodes still have trouble traversing Qodot's collisions as opposed to other ConcavePolygon collision shapes. Your physics FPS should not need to exceed 30 or 60 for accurate collisions on our maps.
#48 I updated the plugin.cfg string to 2023.1.0-prerelease because I like that format, and I will be making a github release following that format.
Anyway, that's all I've got. I wanted to start what I thought was super important to investigate. I would love to hear:
your thoughts (in general :3)
any bugs you've been waiting to be fixed (including godot-side bugs)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Qodot's racked up a lot of bugs of late. I'd like to round up the biggest offending bugs in this discussion.
If you have any experience with these bugs, or want to quickly test your setup for these bugs, that'd be greatly appreciated. Don't forget to double check if you're using the latest Github repo version of Qodot, since that's what we're testing right now.
Let's begin:
Being worked on already
#42 I just pushed a fix to resolve "build def text" on config export. Help me test this out! It's live on the master branch right now.
Still broken and waiting for someone to take it
#33 Is broken geometry still an issue for people using skip brushes? Yes see issue for more details. Skip texture behaviour is currently incorrect and I'll need help evaluating how to fix it ;;
#13 Do solid classes still have grossly inaccurate vertices? Or can people build them without issue? Yes this is still a known issue as reported by a few users.
Solved
#46 Let me know if your CharacterBody3D nodes still have trouble traversing Qodot's collisions as opposed to other ConcavePolygon collision shapes. Your physics FPS should not need to exceed 30 or 60 for accurate collisions on our maps.
#48 I updated the plugin.cfg string to 2023.1.0-prerelease because I like that format, and I will be making a github release following that format.
Anyway, that's all I've got. I wanted to start what I thought was super important to investigate. I would love to hear:
Beta Was this translation helpful? Give feedback.
All reactions