Batch Compiler v3.0.0 Beta - NemPosted: Aug 4th, 2004 - 1:54:39 am

I've uploaded a shinny new version of Batch Compiler written in C#. The new v3 series maintains the same look and design as the v2 series (in fact the main screen looks the same so I won't even bother posting a screen shot) but it has a much more robust specification management system. This is a beta release so please download it, try to break it, and then tell me how you broke it. I've rewritten and added specifications for all the various mapping programs I know of (HLFix, Map Backup, RESGen, Quake Tools, Zoners Tools, Zoners Tools p15 etc.) so keep an eye open for incorrect parameters as there may be a few floating around.

Users new to mapping are going to want to use the "Zoners Tools Normal" specification and experienced users will want to use the "Zoners Tools Advanced" specification. The main difference between the two specifications is simply the tools that make them up.

You can grab the new version here. If you have any suggestions for Batch Compiler feel free to let me know.

Modified: Mar 11th, 2005 - 1:50:32 pm[ 32885 Views ]

[ 1 2 3 4 ]

1. NemModified: Aug 8th, 2004 - 1:35:42 pm

A small bug has been found in Batch Compiler. It caused the batch section of all specifications to generate an error on the last batch command (you may not have noticed it but it is there). Use the same download to get the fix.

2. NoBodyModified: Aug 8th, 2004 - 3:38:52 pm

i also found some bugs, they are in the spec files i fixed them and made som updates to the spec while i was ther (just finished now)
for a full list of what i changed you can look in the readme.txt
hop you will accept them as official spec files :)
updated spec

by the way the main feeld in bc3 is white when using it on win2kpro

3. NemPosted: Aug 8th, 2004 - 7:57:13 pm

Thanks, I never had a chance to extensively test the specification files (just writing them was a fair bit of work). I will take a look at them and upload them as soon as I get a chance. (Just got back from paint ball so I'm kind of sore...)

4. NoBodyPosted: Aug 9th, 2004 - 12:56:03 pm

i just did a update more to the spec.
last time i made some sacrifices so ripent would support opt_entdata but in the new version of opt_entdata i can run freely also ther where also some other changes made look in the readme under part2 (just added it to the same zip file as last time)

5. NemPosted: Aug 9th, 2004 - 1:11:40 pm

The ZIP file is exactly the same as the last ZIP file (are you sure you uploaded it?)

6. NoBodyPosted: Aug 9th, 2004 - 1:22:20 pm

it is now, i should realy learn to upload be for i post and not the other way around japanease

7. NemPosted: Aug 9th, 2004 - 4:28:57 pm

OK, I looked at your changes and I approved of most of them. The changes I approved of have been added to my specification files (and you have been given credit of course, thanks for all the work).

Some small changes I did not approve of (such as -noinfo checked by default) and I did not really reorganize any of the specification files (though I may look at that latter, the main reason to keeping them alphabetical was just for sanity while I was writing them). Some changes were not really necessary, for example the ColorBox can write in both 0.0 to 1.0 format and 0 to 255 format. There was an invalid parameter in your Opt_EntData specification (-nolights was used twice). I rewrote many of the Opt_EntData hints because they had several spelling mistakes and wording and punctuation issues.

The new specifications are not yet included in BC's download. You can, however, get them through BC's update feature (in the Help menu). Backup your specifications if you don't want them to be overwritten.

I will add them to BC's download shortly, just want to make sure they are error free.

Nem

cool

8. NoBodyModified: Aug 9th, 2004 - 6:12:39 pm

he he i have been a bit lasy on the how Opt_EntData i admit i an just waiting around for the last isuess to be fixed befor cleaning that stuff up.

i didn't know how to switching the colorbox to 0-255 you didn't update the spec info when i last checked apple

one question thow why did you not put opt_entdatas no log in to the shared?

9. NemPosted: Aug 9th, 2004 - 6:30:52 pm

I want to keep everything modularized and independent, so "Zoners Tools P Series.bci" should have nothing to do with "Opt_EntData.bci". References should only be made to included files and at the highest level possible. This is just a convention though; you are welcome to do what you want with your own BCS files. I can't guarantee that future BC versions won't have more stringent tests though.

The specification tutorial is pretty close to completion, I've just been slowly working on it when I have time. I will try to finish it off soon.

10. BluefangPosted: Aug 10th, 2004 - 12:12:26 pm

Currently the way Opt_EntData is set up is it requires:

opt_entdata.exe <mapname> <parameters>

so the execution line in the .. needs to be changed to something like this:

"\"${StagePath=Opt_EntData}\" \"${FilePath}\\${FileName}\" ${StageParam=Opt_EntData}\n"_

(or what ever the proper syntax is. I was stumbling in the dark when I was changing it but it seems to work)

I've also modifyed the ZHLT normal.bcs to include HLFix and exclude RipEnt (to keep easy 'easy')

I uploaded them here:
http://rollinit.com/sparky/Half-Life/Specifications.zip

I also have a compile tool package designed for the Zoners Tools p series.
it has beed modifued to use the HLRAD from the p13 version because (from what I have heard) there are some bugs with the p15 version.
it also contains the latest versions of the other tools (including Opt_EntData) and I have modifyed the documentation to reflect theese changes.
http://rollinit.com/sparky/Half-Life/chlt_1.7p15_radp13_complete.zip

I hope you don't mind, but I have repackaged your batch compiler for a tutorial I wrote. it include the new spec files and the compile tolls I just linked (but I removed the Q-Tool and ZHLT Legacy support)
http://rollinit.com/sparky/Half-Life/BC3_complete.zip
here is the tutorial
http://www.chatbear.com/board.plm?a=viewthread&b=9&t=983,1089396813,9185&s=0&id=681099#13

11. BluefangPosted: Aug 11th, 2004 - 2:04:10 pm

*cough*

erm, I just atcually updated all 3 of those files.

-I corrected the previously added 'pause' command at the end of the BCS files
-I added a -texdata switch to Opt_EntData for the upcoming release (is currently remarked out)

12. NemPosted: Aug 11th, 2004 - 2:13:01 pm

Ok, I've reordered the Opt_EntData command line as shown (it is part of the auto update feature but not the installers yet) should I be adding the -texdata option to Opt_EntData?

No specification should have the pause command added to it at the end; there is an option in BC v3.0.0 that will add this on the fly.

13. BluefangPosted: Aug 11th, 2004 - 4:02:57 pm

alright, I didn't see the pause console option.

as for the -texdata switch, no, you probably shouldn't add it just yet. the next revision of the tool hasn't been released quite yet. I only put it in as a place holder.


and not to be pesky, but have you taken any thought to my perposed changes to the nzhly normal settings (addition of HLFix and removal of RIPEnt)?
for that matter, I think it might be a good idea to add HLFix to all of the BCSs. it kind of makes the BC a stand-alone application. it's also esier on the mapper because they don't have to rember to export their map every compile.
it's simple enough for the mapper to set up. all they need is the wad.txt and probably to turn on 'no correction' (because a good map shouldn't need to be corrected).

The removal of RIPEnt could be argued. it is a part of the base ZHLTp15 but none-the-less it is still an advanced tool. Beginners to compiling certainly won't need it and it might only confuse them.

14. NemPosted: Aug 11th, 2004 - 7:44:46 pm

I don't want to add HLFix to the other BCS files simply because it adds another level of complexity. While it is true that what it does is very simple (converts a RMF file to a MAP file) its options could be considered advanced (though I guess you could say that for the compilation tools to); running makewad.exe isn't exactly intuitive either. HLFix is Hammer specific and there are other editors out there; what is a QuArK user going to think when HLFix can't find his RMF file?

Those are, however, just my opinions. I think you could make a valid argument either way so for the sake of consistency I'd rather leave everything just the way it is. Users are just used to it.

15. SlackillerPosted: Aug 12th, 2004 - 5:40:27 pm

Nice job Nem. I like alot of the new options.
cool

[ 1 2 3 4 ]

You must be logged in to post a comment.
New users can register here.
Nem's Tools v2.0 © 2006 Ryan Gregg.
Execution time: 0.026281s; Queries: 17.
dishes served.
Powered by The Wavelength.

Valid XHTML 1.0 Transitional Valid CSS
π