XP:
Originally Posted by Kornman00
Vista:
Start>Control Panel>System and Maintenance>Problem Reports and Solutions>Find Halo report at specific date/time and copy to clipboard
W7:
Start>Search for "View all problem reports">Find Halo report at specific date/time and copy to clipboard
That stuff?
Yes, that is correct.
Fixed. Wasn't resetting a few things when there was a re-importSorry i'm a bit late with this, but there's one more bug for CheApe.
Also, with the shader_postprocess_collection tag, where WERE you going with it? Compiled into a map, or just a tag loaded externally?
The tag was to be built into cache files so that people didn't have to use external files like you initially had with your post-process demo
Ah ok then. I'll probably still have external shaders aswell, for global effects, with compiled shaders for map specifics, but that's for another time :P.
About the lightmap thing, I would code it myself, if I knew XML, but I don't know any program languages except some HaloScript.
If someone could generate a library package with support for the lightmap functions I requested so we can at least find out what happens, I'd greatly appreciate it. Again, I don't know any programming languages at all. Sorry guys. I just want to see how well it works. I have this hypothesis it will work just fine, but I want to see to be certain.
If I were to program it, how would I go about it? I might ask around to see if there's people that could code it, but they'd need to know to what specifications and how.
OpenSauce is not written in XML, nor is it even possible to write a program in XML. OS is written in C++, the only part of it that uses XML files is when defining custom tag groups. I don't know what your fascination is with XML.
Did you just completely skip over or disregard my post?
If somebody is going to go through the trouble of telling you how to do it, they might as well program it themselves.
The part needed to add the script command is done in XML, but it needs to reference the stub code in OS itself for the solution to work, for example, the index for the script and what not.
I was asking if someone could please program that "connection point" between the stub code and the end-user by programming the XML part knowledgeably.
And I didn't mean to skip over your post or be an asshole.
Dude...someone doesn't just sprinkle magic dust on some code and all of a sudden things work. Someone would actually have to reverse engineer the game engine to figure out how it goes about updating to the render current lightmap, then program a script function in C++, as thats what the codebase is written in, to force that update to happen with a new lightmap. Things just don't appear out of thin air
Fine I give up. I suggested the idea because I thought it would be fairly simple to get in-game, not knowing any programming languages. I thought that the current rendering part of the engine could handle it as-is and that all it would require was just coding into Open Sauce. Since it's obviously more complicated than that, or so it would seem, I'm done with it. I'll just assign my 64 lightmaps to 64 BSPs and make a huge filesize map and be thankful for that, even if it's at the expense of others for having to download such an attrocious filesize just to switch lightmaps more smoothly.
It shouldn't have to be that way. I still think it can be done, yet I'm stuck with "what is" because I'm a n00b that can't code a thing outside of Halo. I'm just stupid like that. I've never been good with coding or modeling (not that that even matters) or any of that stuff.
I'll just stand back and read from now on, since I feel so worthless and unwelcome here in this thread. After all, it's not my area of expertise, now is it?
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Bookmarks