VILE's Vertex Box ~ *VERSION 0.2 OUT NOW* ~Read OP For Changelist~

[DoctorFlux(Mariodk)]

awesome what do you have in mean all the vegetas from all sagas + SSJ?
i just requested it in vertex request boards since last i heard you dont got the files and beyondyou was slacking

[DarkPikachu]

It doesn't really answer my question.
The program only answers to an MDL0 file. However, it crashes when I use the original MDL0 like "explained" and the same thing happenned to Jack. So If it's neither a MDL0, nor any other file, then there must be a problem somewhere.

curse me if I'm late on explaining this, but AIS runs brres files...

EDIT: above comment prbly was not needed...
sry I don't use your program vile

[VILE]

curse me if I'm late on explaining this, but AIS runs brres files...

EDIT: above comment prbly was not needed...
sry I don't use your program vile

No problem, AiS does run off brres/pac files.

[Ricky (Br3)]

This will get me back to vertexing...

[BlueBrain]

full support?
no need to patch every polygon one by one?

must try.

[Ricky (Br3)]

full support?
no need to patch every polygon one by one?

must try.

Bleach hack coming our way?

[Miacis]

curse me if I'm late on explaining this, but AIS runs brres files...

That's like waaayyy off what I'd asked. I know that AiS converts BRRES, thanks. Since I wrote a tutorial for a DAE-based method, I should know by now.
I was talking about VILE's program working quirky with an MDL0.

Anyways, let's try it again with v 0.2 ...

Edit : What a surprise. I get the exact same error.

So yeah, clarifications on that step please ?

4. Put the MDL0 file you converted with AiS in with the OBJ files and VVBox and name it "original.mdl0"

I mean, it's not like it's the third time I asked, and that both Jack and I asked the same thing in the Admin section ...

Either that step is really porrly explained, or we'll need a few clarifications on what exactly do we need for settings to export the OBJ files. I really don't think the issue could be coming from anywhere else considering how short that mathod is.

[VILE]

That's like waaayyy off what I'd asked. I know that AiS converts BRRES, thanks. Since I wrote a tutorial for a DAE-based method, I should know by now.
I was talking about VILE's program working quirky with an MDL0.

Anyways, let's try it again with v 0.2 ...

Edit : What a surprise. I get the exact same error.

So yeah, clarifications on that step please ?
I mean, it's not like it's the third time I asked, and that both Jack and I asked the same thing in the Admin section ...

Either that step is really porrly explained, or we'll need a few clarifications on what exactly do we need for settings to export the OBJ files. I really don't think the issue could be coming from anywhere else considering how short that mathod is.

Sorry, yeh that step is poorly written (I never noticed it before).

This is what you need in the VVBox folder:
- The original MDL0 file (straight from a fresh pac file) and name it "original.MDL0".
- The OBJ you created from the dae file AiS gave you, name it "original.obj".
- The edited OBJ, name it "new.obj".

I will rewrite the readme with the next release.

[DarkPikachu]

hey Vile...
that's in Python right??

why not merge it with Tkinter and give yourself a dialog box to open the MDL0 and obj files :/

I'm thinking you just set a button to click for the open dialogs
(one for MDL0, the other for OBJ)

instead of having to name the files independently


from Tkinter import *

mdl0 = askopenfilename(filetypes=[('Brawl MDL0', "*.mdl0")])
obj = askopenfilename(filetypes=[('Wavefront', "*.obj")])

[VILE]

hey Vile...
that's in Python right??

why not merge it with Tkinter and give yourself a dialog box to open the MDL0 and obj files :/

I'm thinking you just set a button to click for the open dialogs
(one for MDL0, the other for OBJ)

instead of having to name the files independently


from Tkinter import *

mdl0 = askopenfilename(filetypes=[('Brawl MDL0', "*.mdl0")])
obj = askopenfilename(filetypes=[('Wavefront', "*.obj")])

Its in C#, I thought you knew I didn't know Python. Embarrassing as it is to admit, I don't know how to create a basic GUI (this includes open dialogs), I've been meaning to look into it, but I have been a bit lazy.

[DarkPikachu]

Its in C#, I thought you knew I didn't know Python. Embarrassing as it is to admit, I don't know how to create a basic GUI (this includes open dialogs), I've been meaning to look into it, but I have been a bit lazy.

hey... don't be embarresed by it XD

Tkinter is apparently HARD
you won't believe how much trouble I have to go through to get 1 thing working >:O
why do you think my multi-reference importing on my converter doesn't work yet XD

the only reason I prefer Tkinter is because installing alternatives is a pain in the butt...
if wxPython and PythonCard were included with the Python distribution, I'd use those.

so yea... I'm not a pro either...
the best GUI I've done is my REFT viewer...
and even that sux ballz XDD

[BlueBrain]

we edit the OBJ, or the dae and later export it as a new obj??

[Akiba Red]

we edit the OBJ, or the dae and later export it as a new obj??

Export the original as an OBJ, name it original.obj, make the edits, and export again, but name it new.obj.

[Jack H.]

Sorry, yeh that step is poorly written (I never noticed it before).

This is what you need in the VVBox folder:
- The original MDL0 file (straight from a fresh pac file) and name it "original.MDL0".
- The OBJ you created from the dae file AiS gave you, name it "original.obj".
- The edited OBJ, name it "new.obj".

I will rewrite the readme with the next release.

With v0.1, renaming the .brres file would make your program at least kick out a "success" message, even though it didn't work...

You've since clarified that the "original.mdl0" file is, in actuality, the mdl0 file within the .pac file. Tried the same thing with v0.2, and I get the same error. Your second two lines of explanation 'make sense' to me, but perhaps not in the same way you've got it 'making sense' up in your head. Obviously, an OBJ file comes from exporting it within 3ds max, which was using the DAE file.

  Questions:
1) The OBJ file that we export from 3DS Max. We ARE exporting the entire model (every frigg'n polygon highlighted) as the .obj, right? I mean... that was the point of going this route instead of every other route for vertex editing, right?

2) The OBJ file that we export from 3DS Max... What in the bloody freaking hell are the export settings. (and for that matter, the import settings of the .DAE file, in case Miacis and I are just completely bastardizing the entire operation).

Thanks VILE, can't wait (seriously, can you tell?) until this method starts working. Save us a crapload of time.

[VILE]

The upcoming version should require no patching and only an MDL0 file and 1 OBJ file.