Welcome to Smashboards, the world's largest Super Smash Brothers community! Over 250,000 Smash Bros. fans from around the world have come to discuss these great games in over 19 million posts!
You are currently viewing our boards as a visitor. Click here to sign up right now and start on your path in the Smash community!
I really hope someone can figure out that looping flag. There must be something somewhere that tells how many frames a level has...
Might be next release, but haven't started on anything yet. For now, export the audio and re-import. If loop points change, the audio will have to be re-encoded anyways, especially the intro padding.
I'm not familiar with the guide, but I'll look at it. If you could send a 'modified' file it would help a lot.
Please explain. And, I hope it's not what I think it is...
Yes, it's me.
You can, just use the insert button in the model previewer. You may want to copy the first frame before doing so, and re-paste when you're done.
It's not a flag, it's interpolation. The game may be using bezier curves. Inside a compact frame, there are two values: one is the actual keyframe value, the other is a very small decimal number. Changing these to an arbitrary number does no good, so I'm assuming the pattern must be replicated. I'm going to start working on this again.
brings back memories of melee using fox's jump wall jump phantom move 
Find the collision data in the stage pac and use the previewer. Collision data is the .coll part.
Oh, I think I called it the wrong thing. I meant the thing that tells the level how many frames it has. If you change Final Destination to have 64 frames, it will animate for the first 64 frames and freeze until 9600 frames have passed (the original amount of frames).
Well, when you go to replace a texture, when you check off the "Preview" box, you can't see the entire texture that you're trying to replace. It instead zooms in on the upper-left part of the texture as shown on the image below. Enable the preview again, and you see the whole texture again.
I see. There are a few more files stuffed inside the stages, so I wonder if they have anything to do with it...
Haa, got it. It has something to do with image 'resolution'. Photoshop defaults to 72, while Windows uses 96. Changing the image resolution to 96 will fix it, but it's been resolved. Good eye my friend!
I had not reported it as I tricked the program to do it another way, but the "new model" option just doesn't work properly, kryal, take a look at it
Never really used that before... Fixed!I had not reported it as I tricked the program to do it another way, but the "new model" option just doesn't work properly, kryal, take a look at it
just a simple model data .brres don't know why it keeps doing that though
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at BrawlLib.SSBB.ResourceNodes.CollisionPlane.DrawPlanes(GLContext context)
at BrawlLib.SSBB.ResourceNodes.CollisionObject.Render(GLContext context)
at BrawlLib.SSBB.ResourceNodes.CollisionNode.Render(GLContext context)
at System.Windows.Forms.CollisionEditor._modelPanel_PostRender(Object sender, GLContext context)
at System.Windows.Forms.ModelPanel.OnRender()
at BrawlLib.OpenGL.GLPanel.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
BrawlBox
Assembly Version: 0.63.3670.40607
Win32 Version: 0.63.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Administrator/Desktop/BrawlBox%20v0/BrawlBox.exe
----------------------------------------
BrawlLib
Assembly Version: 0.10.3670.40607
Win32 Version: 0.10.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Administrator/Desktop/BrawlBox%20v0/BrawlLib.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
you have to animate the platform to move with it
Download the latest release. Version 0.63b is build 3671.
The topmost items are the models themselves, while the sub-nodes are the model's bones. You would only see them if bones have been enabled. You can highlight/enable/disable them just like in the model editor.
Snap will take the transform matrix for that bone/object and apply it to the camera. This is so you can view attached objects with their in-game/world location.
Disable models until you find which one holds your platform. Then, enable bone rendering and highlight the bones until you find the platform (highlighted bones in this case will be red). To attach it to an object: select the object from the list, select the bone, click the plus '+' button on the bone properties. You can also right-click -> attach the bone.
Well, there might be a reason for that. When converting to RGB565 you lose precision, and in some cases two colors that are very close together may clump into one color. The encoder takes each pixel and first converts it to RGB565 to use as an identifier. So, here's a test: convert the image to RGB565 (not indexed), export to png/tga, import, look at the 'colors' field in the importer. If it's 241 then the CI8 encoder is doing what it's supposed to.
That texture part is for Roader, a Subspace Enemy. I did a Shadow Roader texture a few months ago, and I was using parts of that texture as an example.
Well thanks for explaining the problem. I only stated this since there are many CI8 textures that use 256 color palettes, and almost every one of those palettes have 256 different colors. There are some exceptions though. And of course, a lot of my indexed texture replacing involved SmashBox v0.57.
If the texture has already been indexed, then there's a chance you'll lose a few colors. This is only because of the loss in precision. If using a full-color image you'd most likely get 256.
Hold down shift while right clicking, unless that feature got removed and I don't know it (I don't really Shift+Right click much).
![[TSON]](/data/avatars/l/114/114196.jpg?1360761019){kind=avatar}
That sounds like a good idea. Post it in the issue site.
