SwordsRbroken
Smash Apprentice
- Joined
- Jul 28, 2009
- Messages
- 104
The Icy Battlefield texture has a broken camera, just FYI.
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!
Yeah, it sucks, as it was one of my favorite textures for Battlefield. The camera doesn't scroll at all on the stage, it's just locked in place, and you can't see the underside of the stage at all.Seriously? I just downloaded it to
Do you have the link to this 3.0 version?When I played on Smashville, I did not get the texture at all, it was just regular Smashville.
What texture is that and is it 3.0 compatible?Ok so, if I did this correctly, this texture did not work for me. I actually forgot to put the 04, because I wasn't sure how many there were.
When I played on Smashville, I did not get the texture at all, it was just regular Smashville.
What texture is that and is it 3.0 compatible?
People should post some.Phazon Yoshi's Island and Lost Woods sound interesting, but it lacks pictures. :'(
Oh, and nevermind, that actually was my problem, the _. I forgot it.Do you have the link to this 3.0 version?
You do have to rename them _00, _01, _02, etc
I'm not sure the correct name, I know it's village something, and then I'm not sure if it starts on _00, or _01, but the main idea is to name them all in order.
If I remember correctly thought that stage has a day time and a night time version, no? Maybe?
I'm asking this because I've done this for a ton of custom stages myself, including ones never posted on here before and I'm willing to put them up for download if someone will tell me if that's all I needed to do, don't want to put up stages if it turns out I did them wrong even though I'm pretty sure what I posted is all that needs to be doneCorrect me if I'm wrong, but to make custom stages compatible with 3.0, don't you just have to export the death boundaries(stgposition.mdl0) collision data(MiscData[2].coll) and STPM files from the 3.0 basic stages and import them into the custom ones?
GardenvilleCan anyone recommend songs for Gardenville, FoD battlefield, and Lost Woods?
It'd be sick if we had an FD stage like this except the colors changed during the match. Is that even possible though?
Hey guys is there any tutorial to 3.0-ify the old stages? I've been waiting for Dimensional Battlefield and the Subspace FInal Destination haha. I figured I should try to help instead of wait around.
Try that.Quick guide:
- Download Brawlbox here: https://www.dropbox.com/s/f0yfy4dbbrnz7r6/Brawlbox v0.70.zip
- Download the stage you wish to port and have the Project M 3.0 counterpart ready.
- Open the Project M 3.0 stage in Brawlbox. Expand ARC 2. Scroll down until you see STPM data.
- Right click on it and choose "Export". http://i.imgur.com/Y8Uc4OZ.jpg
- Right above that (or in some cases a large amount above that), you should find ModelData[100]. Open that up to find StagePosition (or named similarly...sometimes stgposition). Right click on that and Export as well.
- Now close the PM 3.0 stage file, and open up the 2.6b stage texture. Expand ARC 2 and scroll down to the same place.
- Right click on STPM and click "Replace". Choose the STPM data you extracted.
- Do the same for ModelData[100]'s StagePosition
- Save, and you're done.
- You can also use Ctrl+E and Ctrl+R to Export and Replace respectively.
Here's what you do. Record a replay with the wifi set of 3.0 (using the default stage). Then switch your texture to the new one and watch it again. If it doesn't desynch, then it's fixed.Alright here it is. Can anyone test if it is actually 3.0-ified?
Alright I'll do that now(so much work sigh). Also could I also do the same with replacing the STPM and ModelData100 StagePosition with your Subspace Final Destination? I really like this stage and would like to use it. However I read that you only gauged the sizes so it's not accurate.Here's what you do. Record a replay with the wifi set of 3.0 (using the default stage). Then switch your texture to the new one and watch it again. If it doesn't desynch, then it's fixed.
EDIT: Whoops misread, yes there is. The SSS and probably some moreIs the difference between the WiFi build and non WiFi is the RSBE01, or is there more?
There are coding differences and engine/mechanic changes between the two sets, which is why the offline is meant to be played offline. It desyncs wifi.Is the difference between the WiFi build and non WiFi is the RSBE01, or is there more?
I think it is, since you can play without desynchs on wi-fi just by replacing it.Is the difference between the WiFi build and non WiFi is the RSBE01, or is there more?
You might need to do a little bit more for that stage since I haven't updated it since 2.1. Demo 2.5 was when they switched from the custom model to the Melee import and changed the collisions to match, and I never updated this stage with those changes. The collision is probably even more different now.Alright I'll do that now(so much work sigh). Also could I also do the same with replacing the STPM and ModelData100 StagePosition with your Subspace Final Destination? I really like this stage and would like to use it. However I read that you only gauged the sizes so it's not accurate.
You might need to do a little bit more for that stage since I haven't updated it since 2.1. Demo 2.5 was when they switched from the custom model to the Melee import and changed the collisions to match, and I never updated this stage with those changes. The collision is probably even more different now.
When I was talking about eyeballing the size, I was talking about adjusting the stage model to fit within FD's collisions. This stage would have been non-desycnhing with FD back in 2.1. I was mainly referring to the way that the bottom of the stage turns transparent, which could be visually confusing since the bottom would have solid collisions on that part.
But yes, to answer your question, it is definitely possible to update that stage for 3.0. If the stage has changed size between 2.1 and 3.0 (I don't know if it has; just speaking hypothetically), then you might need to shrink or enlarge the subspace model to match the collisions.