SADX/SA1 Hacking/Modding

making steady but slow progress on the model exporter. All I have to add now is texture coordinate support and fix the data totals. Yay!

 

<!--quoteo--><div class='quotetop'>QUOTE </div><div class='quotemain'><!--quotec-->In other news, I've made a screen layout viewer/editor for SADXTweaker (not released yet). However, currently the only data in this format that has been located is for AVA_BACK.PVM. I would also like to have an option to import an image file, but I'd have to figure out how to make Puyo Tools create PVRs and a PVM for me.<!--QuoteEnd--></div><!--QuoteEEnd-->

Don't use Puyo Tools for creating the PVRs; use VrSharp instead (just add a reference to VrSharp.dll and you should be able to access its methods for creating them).

 

quads are pretty simple, just split them into 2 triangles. Read the first three, then read the last three

 

<!--quoteo(post=430289:date=Mar 23 2010, 03:38 AM:name=Dude)--><div class='quotetop'>QUOTE (Dude @ Mar 23 2010, 03:38 AM) <a href="index.php?act=findpost&pid=430289"></a></div><div class='quotemain'><!--quotec-->[image]

making steady but slow progress on the model exporter. All I have to add now is texture coordinate support and fix the data totals. Yay!<!--QuoteEnd--></div><!--QuoteEEnd-->
I had an Idea, if it's possible, maybe the centre of the circle there could be empty, and the background image change to the selected character? Is that do-able?
I've gotta try that level editor some time, though.

 

I've got it to the point where it will reliably export triangle strip data from an obj file. I need to fix the parser to parse and properly handle the texture coordinates, and integrate OBJ2VT into the main program. once texture coordinates are added, completely custom levels and character models will be very easy to implement.

<a href="http://www.youtube.com/watch?v=_oKdTs1V4Ms" target="_blank">youtube example here</a>

 

Amazing progress.

Question about the strip drawing code, are you drawing the strips like so:
Given a strip list of: 0 1 2 3 4 5 6 7
It'd be:
[0 1 2]
[2 1 3] (not [1 2 3])
[2 3 4]
[4 3 5] (not [3 4 5])
...
etc.

 

I'm not drawing them, I'm having HTGEN make them. I'm pretty sure its going [0 1 2] then if it needs to draw the next poly in the opposite direction, it breaks into a new strip.

 

(Dude, was referring to MM. HTGens would do this anyways because this is pretty much a standard when dealing with tri-strips.)

If the strip is stored as: A B C D E F



ABC would draw fine, whilst BCD would be drawn in the opposite direction, so it needs to be CBD.

That's one thing I remember, the other thing is, if the # containing the strip total is < 0, then the even triangles are inverted, otherwise if the strip total > 0, the odd ones are inverted. (First triangle is triangle 0, so we treat it as even).

 

I've tried giving it negative strip_total values, it crashes every time. Am I doing something wrong?

 

<!--quoteo(post=435186:date=Apr 1 2010, 01:40 AM:name=Dude)--><div class='quotetop'>QUOTE (Dude @ Apr 1 2010, 01:40 AM) <a href="index.php?act=findpost&pid=435186"></a></div><div class='quotemain'><!--quotec-->I've tried giving it negative strip_total values, it crashes every time. Am I doing something wrong?<!--QuoteEnd--></div><!--QuoteEEnd-->

I don't remember... I might be thinking of SA2's model format. SADX might lack this feature.

 

<!--quoteo(post=435189:date=Apr 1 2010, 01:45 AM:name=MainMemory)--><div class='quotetop'>QUOTE (MainMemory @ Apr 1 2010, 01:45 AM) <a href="index.php?act=findpost&pid=435189"></a></div><div class='quotemain'><!--quotec-->It seems all that accomplished was making the UVs totally screwed up. Like they're tiling 100 times more than they should on the Speed Highway buildings.<!--QuoteEnd--></div><!--QuoteEEnd-->

But are they the correct orientation? Might be the UV divisor?

 

<!--quoteo(post=435191:date=Apr 1 2010, 01:50 AM:name=MainMemory)--><div class='quotetop'>QUOTE (MainMemory @ Apr 1 2010, 01:50 AM) <a href="index.php?act=findpost&pid=435191"></a></div><div class='quotemain'><!--quotec-->No, some of the textures are still going in the wrong direction.<!--QuoteEnd--></div><!--QuoteEEnd-->

Well isn't each value in the strip an index?
So shouldn't you be passing the index to the UV as well?

You pass the strip counter # instead... I forgot how the UV data was stored. Wasn't it per vertex?

Single3ToVector3(objects(h).Attach.Vertex(objects(h).Attach.Mesh(I).Poly(j).Stri
p(k + 2))), _
Single3ToVector3(objects(h).Attach.Normal(objects(h).Attach.Mesh(I).Poly(j).Stri
p(k + 2))), _
objects(h).Attach.Mesh(I).UV(currentstriptotal + k + 2).U / uvscale, objects(h).Attach.Mesh(I).UV(currentstriptotal + k + 2).V / uvscale))

to

Single3ToVector3(objects(h).Attach.Vertex(objects(h).Attach.Mesh(I).Poly(j).Stri
p(k + 2))), _
Single3ToVector3(objects(h).Attach.Normal(objects(h).Attach.Mesh(I).Poly(j).Stri
p(k + 2))), _
objects(h).Attach.Mesh(I).UV(objects(h).Attach.Mesh(I).Poly(j).Strip(k + 2)).U / uvscale, objects(h).Attach.Mesh(I).UV(objects(h).Attach.Mesh(I).Poly(j).Strip(k + 2)).V / uvscale))