mzxrules

Understandable. It seems as if the 01 command stores all the same values the 02 one does, except they are unused save for the coordinates. I found? camera roll value. wwrr ffff [aaaaaaaa] [xxxxyyyyzzzz] [????], where r is roll. It's a signed byte value.Positive values rotate the camera counter-clockwise (image spins clockwise).Negative values rotate the camera clockwise (image spins counter-clockwise).-128 is equivalent to 180 degrees rotation.

Angle of view is what creates the zoom effect correct? Ran some tests and it seems only the 02 command actually affects the field of view angle

This only makes me want to figure out how this cutscene works. Which in other words means yes.

This would be so much easier if I knew what I was doing with OpenTK.

Oh also, figured out one of the unknowns to the 02 cutscene command entries ww00 ffff [????????] [xxxxyyyyzzzz] [????]ffff = frames to spend transitioning to the next point. This value seems to be frequently set to 1E. Also, I'm messing with your experimental cutscene viewer. Gonna see if I can simulate a cutscene.

Not sure what cutscenes you are referring to. 00000003 is Title Logo, actor 0171 object 014A. Action 1E fades in, Action 1F fades out. Both have a 1 frame duration.

Actor 56 changes the currently playing song. Action -1 = Song to play.For example, the Boss Theme is 1B, so the action param must be set to 1C.

A site that has to communicate legal matters to children

Does wearing a mask work the same way?

How do textures for map files work?

Yaz0 Compression/Decompression algorithm for C#. Ported from C? code found at http://www.amnoid.de/gc/index.html http://pastebin.com/nvKLmRti The intended usage is byte[] Decode(FileStream sr, int yaz0BlockSize) to decompress a yaz0 block, where FileStream is assumed to be positioned at the start of the compressed yaz0 block. int Encode(byte[] src, int srcSize, FileStream dstFile) to compress and save a yaz0 block, where the returned value is the size of the compressed file in bytes (don't think it includes the header as I only just added some code to print out the header).

Where is this current listing of actors that is 99% complete?

You may have some trouble creating a functional wad if you're using Debug Rom the, because as far as I know, nobody has ever gotten it to work.

Most of the gameplay modifications I wanted to make are done. Tomorrow I intend to work on the areas which will supply the equipment screen with some much needed inventory.

I have some small notes on this as the zone out around the exterior portion of Tower Collapse was discussed some time ago in #zelda as there was a trick discovered which allowed you to reach the lowest platform. Bascially, under normal circumstances if you jump out over no collision polygons, you will zone out once Link's Y coordinate passes -4000. If you jump over a collision polygon that has this quick zoneout attribute, it will take the last Y value from when you were standing on solid ground, and test if you've dropped below -400 units. If you take damage mid-air, the Y value will be updated to the coordinate at which you were at when you were hit.

Slept on it, think I can figure out a way to explain it easier to you since you guys are still not understanding the difference. Say you were able to add new records to the table. How many new exits do you add to the game if you add 1, 2, 20 records? How many exits do you lose if you delete 1, 2, 20, all 0x614 records? The correct answer is 0, because the table DOES NOT DEFINE AN EXIT. Regardless of whatever you do to the table the exits will still exist in code, in the scene data, in actors. If you delete a record that an exit was referring to it would cause a garbage result, but the exit IS STILL THERE AND IS FUNCTIONAL. Conversely, if you define a new exit through code or by editing a scene scene, without modifying the table, you do not define a new entrance in which to spawn into a scene. You cannot spawn anywhere else that is not already defined by the table (unless you do something stupid and read past the table). If you delete an exit without modifying the table, you do not delete an entrance. You may get to a point where you can no longer access all the entrances, but they will still exist. The table is not a list of exits, therefore an index value to the table is not an exit indexer.

Except they are wrong, for the reasons above. And it would be a nonsensical argument. The contents of this message can only be accessed via web browser, but you wouldn't call it a Google Chrome message (or your browser of choice) would you?Again, it doesn't matter how you access the values, what matters is the information that is actually being stored. But it's cleaner to say that the 00CD + FFF3 pair defines the exit, and the 00D4 record defines the entrance, because the 00CD + FFF3 pair is what is pushed by the exit, while the 00D4 record that is pulled is used to facilitate spawning within a scene, as again the 00D4 record has nothing to do with the cutscene or the exit directly.

Incorrect. Exits (whether it's a collision polygon, actor, code.asm) do not define an entrance, they merely contain a single index value. It is the so called "Exit List" table which defines the entrances. Without it, the index value has no meaning. The table is what gives meaning to the index value in the first place, and thus to understand and describe what the index value is representing, you must understand what the table is representing because the index value is merely a key into that data. And this the heart of my problem. You (and many others) are not understanding that it is the data that the index is representing that defines it, not how the index is being used. What data does the table hold? A scene, a position. Given that data alone, can you always determine what entrance you will be starting from? Yes, provided that the same scene header is used. Given that data alone, can you always determine what exit you used to reference the data? No, because even if you had only one exit take you to a particular entrance, the data within the table is not enough to uniquely define what exit you came from (ex. only one "exit" can take you to the title screen entrance (0x00D4), but 0x00D4 has the same Scene/Position pair as 0x00CD, which is an entrance you're placed at after another cutscene). And that is why it's incorrect to say that http://wiki.spinout182.com/w/Debug_ROM:_Exit_List is a table of exits. And it's not because I want to show off some intellectual superiority, it's because when I first started looking through to Spinout's wiki, the Exit List made it harder for me to understand how the game worked, and harder to explain the things I was observing with the Wrong Warp glitch.

It's not a program, it's an excel file that requires either Microsoft Excel or Open Office to view. You need to click the tabs on the bottom to switch between sheets. I didn't think I would need to add a readme on how to use a spreadsheet program. Object vs Group is a completely different thing because you're trading one generic term (group) for an even more generic term (object). An entrance CLEARLY has a functional difference than an exit, and thus should be properly expressed. You are not really helping by not taking the extra effort in explaining the difference.

Now all you have to add in are some pumas.

If you had actually clicked the link and followed my instructions, you would have seen that there already exists such a list in my tables, though it may be a little confusing to read as I've removed redundant indexes (ex. 0000 - 0003 are logically equivalent, so the lowest index (0000) is the only one listed as this value would be the one passed by exits). Also, I'm very confident that the tables are identical across versions as V1.0's entrance table has the same number of records, there are still references the scenes which are no longer in the rom, and lastly because Master Quest is merely a dungeon mod. There is no logic in your reasoning behind calling the index value an exit (aside from "tradition"), because you aren't thinking about what the data actually represents. To elaborate, I want to start by defining what I believe to be accurate definitions for entrances and exits with respect to the game world: An entrance is an entrance point into a scene. An exit is point within a scene that allows you to leave the scene into the same or another scene. Now, the index value is a reference to a single record in our so called "Exit List". And if you look, you'll see that each record defines a Scene number, and a Position number, which in turn defines what scene file to load, and the position number translates into coordinates within that scene (a.k.a an entrance). Clearly there is no proper relationship between an index value for that table, and an exit, so they shouldn't be called exit indexes.

Tried doing something really stupid, but it has given me an idea for an easter egg Edit: Inside Ganon's Castle is done, save for fixing the exits such that you can't leave.

giadrosich, check out https://www.the-gcn.com/topic/2374-mzxrules-notes-on-ocarina-of-time/?p=37460 There's a complete table of all the entrances within the game, in the FW table. Also they're not exits.

Believe I discovered a new cutscene command. 00000009 00000001 XXXXXXXX YYYYYYYY ZZZZZZZZ? No clue what it could be. Found near the end of the dispelled barrier cutscene (offset 1DA40 from start of the Inside Ganon's Castle scene in v1.0)