Bumbleson on 16/5/2005 at 10:44
I agree that there's no need to explain each one (ha, I don't even understand them all! :sweat: ), but I think the basic problem remains. It should be possible to explain single actions or conditions on seperate pages when they are special enough or have pitfalls to consider, and those pages should have descriptive names. But I can't think of a suitable naming scheme. Take this action for example:
Analog flicker object(s) [LinkFlavor] Brightness:Min= [Float] Max= [Float] OffTime:Min= [Float] Bias= [Float] Max= [Float] OnTime:Min= [Float] Bias= [Float] Max= [Float] Flicker:Min= [Float] Max= [Float] BetweenFlickers:Min= [Float] Max= [Float] ; [Int] repet
How would you name a wiki page that explains it without the risk of mixing it up with another one that does something similar?
Bumbleson on 16/5/2005 at 18:08
Ok, I think I've figured out a simple enough category system. I still don't know how to name pages that explain single properties, so I'm going to leave that out for the moment.
@Crispy: Since I've obtained my list of properties :tsktsk: conditions and actions by OCR directly from the T3Ed screen, the TickRate info you extracted from the logs is missing (sorting them by hand would have taken me ages :p ). While I don't think it's absolutely essential, it might still be useful information for advanced designers, but I don't know how to preserve it automatically. Would you mind if it gets lost temporarily until I have time to figure out how to include it again?
rujuro on 18/5/2005 at 20:01
Let me know where you're confused, and no problem.
doctormidnight on 18/5/2005 at 21:13
Quote Posted by rujuro
Let me know where you're confused, and no problem.
The part that says:
To fully rebuild the metafiles you will need every .wav in the game unpacked in the sounds folders.
How does one go about doing that? And what about directory structure, does it have to stay the same?
rujuro on 18/5/2005 at 21:36
I believe you need to unpack all the sound files from the existing metafiles using sound drone or something like that. I don't think directory structure is important (I believe I moved a .wav around and it still found it), but they DO need to be in the Sound folder.
Someone can correct me if they discover I'm wrong about the directory structure.
doctormidnight on 18/5/2005 at 21:41
OK, add that to the wiki when you get a chance. On a slightly related note, once the audio has been extracted with Sound Drone, can they be previewed (i.e., played) in the schema browser or not?
Edit: Here is a stable link on my server for Sound Drone if you need it for the wiki:
(
http://www.sherlockholmesarmy.net/ttlg/DXIW_Sound_Drone_v1.0_BETA.exe)
Zillameth on 18/5/2005 at 22:07
Is it possible to control which metafiles wavs are put into? If it is possible, we could force the script to create a new metafile containing only new content. Or maybe we could use SchemaMetafile_Memory.csc, which appears to be empty by default.
This would allow FM authors to distribute their custom schemas and sounds without the need of attaching them to one of these huge preexisting files.
rujuro on 18/5/2005 at 22:59
You define the metafile it gets placed in in the schema browser. It's a pulldown menu, so I think we're limited to the original metafiles.
We discussed using the Memory Metafile in another thread. I'm a little gunshy on this, since it's hard to say how that might effect performance. I assume that means it's placed in RAM. Couldn't hurt to try I guess.
Crispy on 19/5/2005 at 01:49
Quote Posted by Bumbleson
@Crispy: Since I've obtained my list of
properties :tsktsk: conditions and actions by OCR directly from the T3Ed screen, the TickRate info you extracted from the logs is missing (sorting them by hand would have taken me ages :p ). While I don't think it's absolutely essential, it might still be useful information for advanced designers, but I don't know how to preserve it automatically. Would you mind if it gets lost temporarily until I have time to figure out how to include it again?
Sorry for my lack of postage... I've been insanely busy as of late (and will continue to be so for another week).
Really, I don't even know if the TickRate stuff is useful or not (I only have theories about what it does). I included it "because I can". :p
It's a wiki; it belongs to the community, not to whoever happened to create the page first. Do what you will with it (apart from trashing it, naturally). :)
