Previous Page | Next Page

by Knurek at 12:43 PM EDT on March 9, 2009
Can someone check my logic? Either I'm making a very stupid mistake somewhere or vio2sf doesn't support _lib tags properly.

1. For games using multiple SDATs, create a rip on the *largest* SDAT, unpack 2sflib, zero out everything after SDAT starts, repack as driver.2sflib.

2. Take any SDAT, append 2sf header (0x9c910e00 + size of sdat), bin2psf to sdat_name.2sflib

Everything works so far, if I rename sdat_name.2sflib to .2sf, add _lib=driver.2sflib tag and try to play it works fine (provided there's a 0x00 song of course).

3. Take CaitSith2 generated mini2sf, add _lib=driver.2sflib, _lib2=sdat_name.2sflib tags.

The problem is, files made like that don't play. At all. Changing lib order only crashes vio2sf...
Anyone seeing anything here?
Reply to agu fungus by Camo Yoshi at 4:49 PM EDT on March 9, 2009
The reason (I presume, at least) to call the 2sf player Highly Nitric, I because the Nintendo DS was codenamed "Nitro" before release.

Nintendo History class is over! Remember, Your NES homework is due tomorrow!
by CaitSith2 at 5:13 PM EDT on March 9, 2009
I tried similar _lib / _lib2, and it does not seem to be implemented properly, according to the standards.

Proper procedure of _lib loading.

_lib = Main rom with everything required.
mini2sf = patch rom that changes the song. Usually one or two bytes patched.
_lib2, _lib3, etc.. = patch rom that changes other bytes, or loads in other data in place of existing data.

So basically, _lib is loaded first right into ram.
_lib2 is then patched into the memory that _lib takes up. If this would exceed boundaries that _lib took, reallocate the size of _lib.

Then mini2sf is applied on top of _lib, same procedures.

This really should have been implementted into the player even if it wasn't used at the moment. If you need some help, look at the source code of highly advanced. It is implemented there.
by marioman at 5:19 PM EDT on March 9, 2009
@Camo Yoshi: No, the 2SF player is called Highly Whatever because Whatever is a codename for Nitric which is the name the UF never gave it. Any questions?

edited 5:19 PM EDT March 9, 2009
by Knurek at 5:56 PM EDT on March 9, 2009
@CaitSith2: It's weird, since aossf and aodsf plugins by the same person (I think) handle _lib tags according to standards...

Well, having this would shave a few megs off of Sonic Rush and Sonic Rush Adventure sets, so hoping for new vio2sf version. :)
by unknownfile at 2:47 PM EDT on March 10, 2009
i am thinking of renaming it back to highlynitric

because highlywhatever sounds better for something else
by Knurek at 12:42 PM EDT on March 11, 2009
There's a new version of vio2sf, but I'd advise against switching to it for now (stick with 0.17).

There's a bug in the xsflib loading code, and the default behaviour loads mini2sf first and then overlays the 2sflib on to that.

Since mini2sf have the song select code, what you will get is song 0x00 playing for all files.

Obviously an oversight, if you still intend to update (no other changes listed, so really no use I guess) adding _vio2sf_loader_type=1 tag to all mini2sf files will fix the situation.

edited 12:47 PM EDT March 11, 2009
by Arbee at 12:53 PM EDT on March 11, 2009
Knurek: aossf/aodsf work properly because the underlying AO engines do the right thing. For 2sf he uses his own xSF loader (swiping mine would've worked better, but oh well).
a problem has arised by unknownfile at 1:45 PM EDT on March 11, 2009
by Elven Spellmaker at 8:14 PM EDT on March 11, 2009
Ahh, its a big problem indeed...

I congratulate your drawing, it made me laugh, like the nenson one.

Its only about 2 tracks not working properly (from what I can tell), ( i.e. dropping instruments), but apparently is "I't doesn't work" outright...

And it didn't even rip before the updates, so its some improvement.

edited 8:15 PM EDT March 11, 2009

Previous Page | Next Page
Go to Page 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118

Search this thread

Show all threads

Reply to this thread:

User Name Tags:

bold: [b]bold[/b]
italics: [i]italics[/i]
emphasis: [em]emphasis[/em]
underline: [u]underline[/u]
small: [small]small[/small]
Link: [url=http://www.google.com]Link[/url]

[img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message

HCS Forum Index
Halley's Comet Software
forum source