Brawlbox Resources & History

[♤♡◇♧]

I managed to fix a problem I had with the importer for quite a few months.

The problem was that every model I tried to import wouldn't calculate the translations, rotations and scales properly, resulting in something like this:


See the garbage input on Translations ,the NaN on rotations and the 1000000 on scales?

I tried to look what could be the cause of this when I was reminded by a similar problem I had with the Mario Kart Wii .obj importer.
So I opened the .dae in Notepad++ and did the same thing I did to fix the error I had with the .obj importer.
After doing that, I imported the freshly edited .dae into BrawlBox and previewed it.
To my surprise, I got this:


All the Translations, Rotations and Scales were correctly displayed and the model showed like it should.

The only thing I had to do was replace almost all the '.' with ',' (except for the '.' in the texture paths for obvious reasons) and it would display like it should.

Maybe this will help (some) people who experienced problems with importing.

[Carnage]

I managed to fix a problem I had with the importer for quite a few months.

The problem was that every model I tried to import wouldn't calculate the translations, rotations and scales properly, resulting in something like this:


See the garbage input on Translations ,the NaN on rotations and the 1000000 on scales?

I tried to look what could be the cause of this when I was reminded by a similar problem I had with the Mario Kart Wii .obj importer.
So I opened the .dae in Notepad++ and did the same thing I did to fix the error I had with the .obj importer.
After doing that, I imported the freshly edited .dae into BrawlBox and previewed it.
To my surprise, I got this:


All the Translations, Rotations and Scales were correctly displayed and the model showed like it should.

The only thing I had to do was replace almost all the '.' with ',' (except for the '.' in the texture paths for obvious reasons) and it would display like it should.

Maybe this will help (some) people who experienced problems with importing.

lol why does blastoisa has venuseur flower on its back? is that fan made blastoise/ venusaur fusion?

[Segtendo]

lol why does blastoisa has venuseur flower on its back? is that fan made blastoise/ venusaur fusion?

It's a hybrid called "Venustoise"
The model is in Kit's thread.

[BlackJax96]

I managed to fix a problem I had with the importer for quite a few months.

The problem was that every model I tried to import wouldn't calculate the translations, rotations and scales properly, resulting in something like this:


See the garbage input on Translations ,the NaN on rotations and the 1000000 on scales?

I tried to look what could be the cause of this when I was reminded by a similar problem I had with the Mario Kart Wii .obj importer.
So I opened the .dae in Notepad++ and did the same thing I did to fix the error I had with the .obj importer.
After doing that, I imported the freshly edited .dae into BrawlBox and previewed it.
To my surprise, I got this:


All the Translations, Rotations and Scales were correctly displayed and the model showed like it should.

The only thing I had to do was replace almost all the '.' with ',' (except for the '.' in the texture paths for obvious reasons) and it would display like it should.

Maybe this will help (some) people who experienced problems with importing.

You replaced every single "." in the file with a ","? Could you be a little more specific? I want to see if I can code a fix. That might have to do with the "computer specific" thing. I think Pikazz and KTH have the same problem. Do all your computers operate under a different language than English?

[Justin712]

1 - Yes, I always follow your tutorial. Like I said, this SOMETIMES happens, not always

No you didn't. It's very clear you didn't. It does this every time, and it's very easy to fix. Pay attention and listen to BlackJax. It takes two seconds to fix in Brawlbox.

You're very clearly in the wrong here.

[Albafika]

You replaced every single "." in the file with a ","? Could you be a little more specific? I want to see if I can code a fix. That might have to do with the "computer specific" thing. I think Pikazz and KTH have the same problem. Do all your computers operate under a different language than English?

I have the same problem too.

And mine operates on Spanish and English.

[♤♡◇♧]

You replaced every single "." in the file with a ","? Could you be a little more specific? I want to see if I can code a fix. That might have to do with the "computer specific" thing. I think Pikazz and KTH have the same problem. Do all your computers operate under a different language than English?

Actually yes.
I operate under Dutch and I'm pretty sure KTH operates under French (and I guess Pikazz under either Swedish or Finnish).

And yes, it's basically replacing all the "." with "," except for the ones in the texture paths.

[Albafika]

Actually yes.
I operate under Dutch and I'm pretty sure KTH operates under French (and I guess Pikazz under either Swedish or Finnish).

And yes, it's basically replacing all the "." with "," except for the ones in the texture paths.

Just tested it. It works. 

[BlueBrain]

i had same problem and mine is spanish

[Albafika]

i had same problem and mine is spanish

Yes, it seems the "." only works for PCs with their system language in English.

And what do you mean by "Had"?

[♤♡◇♧]

Also, in case you have screwed up bone rotations, like this:


Replacing the bone node date in the .dae file with the data of a .dae exported using one of the bonesets found in the boneset thread, you'll basically fix all rotation problems, shown here:

(My rig still is screwed up, but that's because I'm not that good in rigging and therefor asked Justin712 do to it for me (but this may help with the bone problem he told me about))

[BlackJax96]

I fixed the problem already. I was able to import a dae that had all commas for the float values on my English computer.

Also, in case you have screwed up bone rotations, like this:

Replacing the bone node date in the .dae file with the data of a .dae exported using one of the bonesets found in the boneset thread, you'll basically fix all rotation problems, shown here:

(My rig still is screwed up, but that's because I'm not that good in rigging and therefor asked Justin712 do to it for me (but this may help with the bone problem he told me about))

Now that's just random.

[♤♡◇♧]

.dae files are basically just text files, so that it is editable in Notepad++ in such a way may or may not be that random.

[Eternal Yoshi]

Once you have the model on 3DSMax, anything's possible.

Unless your luck is bad like mine.

[TokoyamiTheDark]

Unless your luck is bad like mine.

Look, I've sought every way to rig one of my models, it just doesn't wanna work right... My luck is as bad as yours, because every day, I continue seeking the errors or bad things that deforms my model away...