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
I have searched for duplicate or closed bug reports
I understand that I am supposed to provide my own legitimately obtained copy of the game
Describe the Bug
Usually attatches your actor's collision mesh to Daxter/around Jak's shoulder. Moves and animates with Daxter, but still appears on/off screen depending on the correct location of the actor's real bounds sphere.
Not a big deal since adding a dummy second bone to give the armature more than one bone fixes it.
Can also cause other issues such as the collision mesh and animation mesh becoming invisible (yet still being in the right spot).
How To Reproduce
Assign a collision mesh to a bone index when writing an actor's collision mesh code, when the armature in Blender has one bone.
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
Collision mesh should attach to the bone index you have written when writing the collision mesh code.
Environment Information
Blender 4.0
Game Version
NTSC 1.0 (black label)
Have you set the game to something other than 60fps?
No
The text was updated successfully, but these errors were encountered:
Acknowledgements
Describe the Bug
Usually attatches your actor's collision mesh to Daxter/around Jak's shoulder. Moves and animates with Daxter, but still appears on/off screen depending on the correct location of the actor's real bounds sphere.
Not a big deal since adding a dummy second bone to give the armature more than one bone fixes it.
Can also cause other issues such as the collision mesh and animation mesh becoming invisible (yet still being in the right spot).
How To Reproduce
Assign a collision mesh to a bone index when writing an actor's collision mesh code, when the armature in Blender has one bone.
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
Collision mesh should attach to the bone index you have written when writing the collision mesh code.
Environment Information
Blender 4.0
Game Version
NTSC 1.0 (black label)
Have you set the game to something other than
60fps
?No
The text was updated successfully, but these errors were encountered: