Supreme Cmdr

The DOCK and DOCKWITH commands do different things. DOCK - tells the object to dock with another object. The option 'time' parameter tells the object to auto-launch after that time expires. This is usually used for crafts docking with stations, but will work for any actor docking with another. DOCKWITH - tells the object to dock with another object. The optional 'vanish' tells the game engine to remove it after it has docked. While the optional "deactivate" tells the game engine to deactivate it (i.e. not do any further rendering or AI processing for it) so that you can "re-activate" it later with the ACTIVATE command in an event. This is usually used for personnel docking with vehicles and such, but will work for any actor docking with another. Also, the !docked event checks if the current object (for which the !dock event is checked) has docked with a "target" object. e.g. [ai] .f1,100,100,100,100,100,100,0 start inactive near cronusz^jmp-23 500 cronus stop events 1 !beginl1 activate this !startup dock orion !detect orion say "GCV-WILDSTAR: ORION, WE ARE REQUESTING DOCKING CLEARANCE" signal f1_dock_request !docked orion signal f1_docked endevents # .orion events 1 !f1_dock_request say "ORION: DOCKING CLEARANCE GRANTED WILDSTAR. PROCEED TO BAY ONE" f1_docked say "ORION: GCV-WILDSTAR HAS DOCKED" endevents[/code]

The support craft definitions - for player crafts - are in the ASSETS.INI file. You can't edit that (or any file in the DATA folder) file due to the MD5 checksum which is used to preserve and protect the integrity of the game's core files. To change the support craft definitions for AI crafts, look in OBJCLASS.SCR. Just like the docs say.

The version of GBS-IV included with UCCE, is only compatible with the UCCE game. So, no, you can't run a script included in the game or build its source and play it with any previous game in the series without experiencing problems. If you have the DVD-ROM version of the game, GBS is in a folder on the media. You can copy it to any folder on your machine. If you have the digital distribution version, it is compressed in GBSIV.ZIP archive located in the TOOLS folder where the game is installed. Just extract it to any folder like. In either case, the GBS distribution contains source scripts for all the scenarios (11 campaign + 111 Instant Action) in the game. Using GBS, you can make minor or major script revisions. e.g. say you wanted to play IA0001 with a Battlecruiser MK2 (or any other cap ship) ship class (look in OBJCLASS.SCR for all object class names) instead of the default MK1, it is a one line change (to the ship class) and a parsing of the script source. Start a text editor (e.g. Notepad) and load the IA0001.SCR file from the SCRIPTS folder Go to line #28 and change "set_craft battlecruiser_mk" to "set_craft battlecruiser_mk2", then save the file Open up a console (START/RUN/CMD) window and change to the folder where you have GBS extracted (e.g. "C:\Program Files\3000AD\Universal Combat Collectors Edition\Tools") From the console window type Prepare IA0001.SCR to parse the script Copy the resulting IA0001.MIS file to the MODS sub-folder (e.g. "C:\Program Files\3000AD\Universal Combat Collectors Edition\Mods") Run the game and select the IA0001 scenario from the Instant Action list When you launch and go to the F9 view, you will see that you are using the MK2 instead of the MK1 carrier. Since you are not overwriting the source scripts already built and included, you can delete this .MIS file if you want to revert to the version included in the game. This is due to the fact that the game will always use the newer file and ignore the older version (in the DATA sub-folder). This is a simplified explanation of course. You can read the rest of this forum, as well as the included GBS docs for other tips. Though the GBS parsers are different, the scripting concepts, tips etc used in all the Universal Combat games are the same. Also: If you have modified the scenario description file (IA0001.DES) file which is displayed in MISCON, you also have to copy it (as-is) over to the MODS folder. This file is not parsed. It is processed in pure text form by the game engine. If you revise (add, remove, edit etc) ANY of the strings used in the "say" and "broadcast" commands inside the script source, then you have to parse the engine's phrase handler by doing prepare phrases IA0001.SCR and copying the resulting IA0001.DAT file to the MODS folder. Then the new strings will be used by the game when the scenario is run. Also, you can create a batch file e.g. BUILDIT.BAT and add the following commands to it. This will automatically do all the steps required for a single script and copy the resulting files to the target folder. prepare %1.scr if errorlevel 1 goto fail prepare phrases %1.scr if errorlevel 1 goto fail goto ok :fail echo AN ERROR OCCURED! BUILD ABORTED! goto exit :ok copy %1*.dat %1.des %1.mis "C:\Program Files\3000AD\Collectors Edition\mods" echo SCRIPT BUILT OK :exit[/code] To create this batch file, just cut and past everything between the "code" blocks into a blank file. Save it as BUILDIT.BAT in your TOOLS folder (or where ever you have GBS extracted). Then to parse a script, from a console window, you would just type build IA0001

For those of you who want to know how the scenarios are arranged in UCCE, you can view the GAME_SCENARIOS.TXT file which shows this. We have an entire forum section dedicated to scripting.

You are using the 2.0 activation site to activate a [2005] product activated with the 1.0 version. Read this.

Starforce changed the activation login server when they released their newer product. For UCG and UCAWA, use the 1.0 activation site For UCSE, use the 2.0 activation site NOTE: This is for versions purchased through BMT Micro or Digital River and only for the titles above. UCSE was the last title to use Starforce. Also, we do not - and never have - used their much maligned disc based protection scheme.

Whoa!!! what the heck have you been?!?!?!

Did you try the transfer option on the Starforce activation page?

Dead thread resurrection coming up. Wolf sent me GameSpot's review of Tarr Chronicles today. I almost pissed myself laughing. Sure, I love sci-fi and space sims as much as anyone here, but seriously, shouldn't the goal be to improve the genre? These bastards doing these foolish games aren't helping!!

IGN informs me that the D2D version of this patch is now online and on their patches page.

I checked the cd-key. You already activated the game twice (see dates below) and on two different machines. Thats why the activation no longer works. Check your email.

The sounds are fine to me. Plus, why should the old sounds not be used? If a weapon sounds one way, its not going to get any better if it sounds another way. Usage of stock library (art, audio assets etc) is common practice; especially for games in a series. Heck, we've been using our stock library for God knows how long now and I only occasionally add new ones or revise existing ones. Change for the sake of change is foolishness.

A number of retailers didn't place their orders in time or didn't order enough units (which is why the game is sold out everywhere). But a number of entrepreneurs on eBay have figured this out. I was notified of a bunch of units on eBay, but nothing prepared me for a $34.99 listing for a game that retails for $29.95 ...thats when I saw a listing for $43.22. Wow. Just Wow.

Send me the purchase email which shows the serial # and I'll check it out.

I have personally deleted two tech support related posts and banned one user from posting for 30 days because he repeatedly created the same topic after it was deleted before. The rules around here have NOT changed. So, if you're new or just rusty on the details, you might want to read up on them again. Also, there is now a tech support ticket system which can be used ONLY if you have SEARCHED the forums and not found an answer. In the coming weeks, the ticket system will also be populated with known FAQ related items. As it stands, there isn't a single issue in ANY of these games that hasn't already been known and/or addressed. Most of those issues boil down to video or audio drivers issues which have nothing to do with the game, and thus will not be addressed by us. Developers can't fix what they can't reproduce. Anyone violating these guidelines, will be banned from posting. No excuses. No exceptions.

Yeah, apart from the still-in-development MMO, Universal Combat Online, the CE collection is the last one in the series I'm afraid. Unless of course ten years from now things change. I have been thinking about following through on my Battlecruiser Next Gen plans though; complete with in-ship levels and whatnot. Maybe some day. But right now, the market for high-end niche games is a bit stale. Plus, I'm bored. With the lighter-fare GALCOM series, I'll get a much needed break I think. Since there are two titles being developed in tandem (and you'll know why, once I announce the reasons and post the first ever shots from Talon Elite and Bravo Team), I've got my hands full until at least 2009 before I decide where I'm going post-Bravo Team. Hopefully by that time, the MMO would have come far enough to be public Beta worthy. And Take2 did a fab job on the materials. I didn't want to skimp on them since this is the last of the series. So I wanted to retire the old gal' in style.

I have released a patch which may or may not resolve this issue. Let me know if it does. I hope it does because I'm not releasing another patch for a two year old product which used to work just fine.

Decided to merge in on common fix related to vertical lines appearing on the screen on ATI cards. This is a driver issue which is even worse on Vista. So I decided to just go ahead and merge it. The D2D version is should be up sometime next week once IGN releases it. So, if thats the version that you have, keep checking their downloads page. I'll post about it once I'm notified that they have released it. This patch requires the August 2006 (or later) DirectX runtime Use the game Updater to download and apply the patch. The online VCF has also been updated. NOTES: If you use the game's Updater, the process will go like this: If you have any version lower than 1.00.07, it will download the 1.00.07 update first. After applying this, you need to run Updater again so that it can download the incremental update to the latest version. You will have to run the Update multiple times to get all the updates to the latest version. If you already have 1.00.07 or higher installed, it will download only the incremental update to the latest version. If you don't want to use the Updater, then you have to check one of the public mirrors for a link to the full patch; which you should then copy into the game's folder and execute from there. Though this latest patch contains a new SETTINGS.INI file, if the Updater downloads the patch but it doesn't run or you discover that it didn't patch, you may need to edit the SETTINGS.INI file in Notepad and make the following changes : version=1.00.15 to version=1.00.16 (or change this to whatever the previous version was) location=. to location=%updater% Then save the file and run the Updater again. WARNING: DO NOT DOWNLOAD THE PUBLIC PATCHES AVAILABLE ON DOWNLOAD MIRRORS IF YOU HAVE THE DOWNLOAD (e.g. DIRECT2DRIVE) VERSION OF THE GAME!! USE THE UPDATER INSTEAD. ONCE THE PUBLISHERS MAKE THEIR VERSIONS OF THE PATCH AVAILABLE, THE UPDATER WILL DOWNLOAD THEM. THE TIMETABLE FOR THOSE PATCH RELEASES IS UP TO THE PUBLISHER DUE TO HOW THEIR PROTECTION SYSTEM WORKS.

I took a quick look at the UCAWA source code (from 2005) and decided to merge in the same fix from UCSE/CE and release it as the final .20 patch. I just tested it on an ATI board and Vista and it seems to work. The patch should be out later next week. I have already updated the VCF.

I have added some recommended IP.Board patches. Everyone needs to scroll to the bottom of the main board page and clear all cookies set by the board. Then log back in (if you weren't logged out when you cleared cookies). Hopefully that should fix the problem until the come up with a new patch. This .2 patch was only released this past week. Go figure.

We're not responsible if the game ceases to work on HW that was released after it was released. UCAWA is no longer supported and there will be no further patches for it. In fact, those lines and flickering you're seeing are caused by newer (thats why this problem was not occuring back when the game was released) ATI drivers. It was recently worked around for UCSE and UCCE in the 1.00.03.01 updates released earlier this week. As for laptops, our games never have - and never will - be supported on laptop chipsets. And guys - yeah both of you - if you're going to post the same frigging thing in the forums, please don't waste our time and resources by regurgitating the same thing in the support ticket system. Pick one or the other.

The latest IP.Board 2.2.2 upgrade borked some aspects of the board especially related to new/read post counters. Hopefully an update is forthcoming as we're not going to be doing any hacking.

This patch requires the August 2007 (or later) DirectX runtime Use the game Updater to download and apply the patch. The online VCF has also been updated. NOTES: This patch uses a different installer. Be sure to confirm the location of your install in the dialog which appears!! This patch is for the DVD-ROM version only. The UCSE to UCCE upgrade (available exclusively through BMT Micro) already has this version applied to it. So no patch is needed. If you use the game's Updater, it will download the patch and apply it. If you don't want to use the Updater, then you have to check one of the public mirrors for a link to the full patch. WARNING: DO NOT DOWNLOAD THE PUBLIC PATCHES AVAILABLE ON DOWNLOAD MIRRORS IF YOU HAVE THE DOWNLOAD (e.g. DIRECT2DRIVE) VERSION OF THE GAME!! USE THE UPDATER INSTEAD. ONCE THE PUBLISHERS MAKE THEIR VERSIONS OF THE PATCH AVAILABLE, THE UPDATER WILL DOWNLOAD THEM. THE TIMETABLE FOR THOSE PATCH RELEASES IS UP TO THE PUBLISHER DUE TO HOW THEIR PROTECTION SYSTEM WORKS. NOTE Games supported: UCCE v1.00.03 Full (Take2 DVD-ROM retail version)

I haven't had the chance to personally test this patch cuz I've been busy. But it should work since it uses the same protection as the previous version. However, if there is a problem with it, let me know. You can always revert to the previous 1.00.03 version by editing the settings.ini file and running the Updater.

This patch requires the August 2007 (or later) DirectX runtime Use the game Updater to download and apply the patch. The online VCF has also been updated. NOTES: If you use the game's Updater, the process will go like this: If you have any version lower than 1.00.03, it will download the 1.00.03 update first. After applying this, you need to run Updater again so that it can download the incremental update to the latest version. You will have to run the Update multiple times to get all the updates to the latest version. If you already have 1.00.03 or higher installed, it will download only the 1.00.03.01 update version. If you don't want to use the Updater, then you have to check one of the public mirrors for a link to the full patch; which you should then copy into the game's folder and execute from there. Though this latest patch contains a new SETTINGS.INI file, if the Updater downloads the patch but it doesn't run or you discover that it didn't patch, you may need to edit the SETTINGS.INI file in Notepad and make the following changes : "version=1.00.03.01" to "version=1.00.03" (or change this to whatever the previous version was without the quotes!) Then save the file and run the Updater again. WARNING: DO NOT DOWNLOAD THE PUBLIC PATCHES AVAILABLE ON DOWNLOAD MIRRORS IF YOU HAVE THE DOWNLOAD (e.g. DIRECT2DRIVE) VERSION OF THE GAME!! USE THE UPDATER INSTEAD. ONCE THE PUBLISHERS MAKE THEIR VERSIONS OF THE PATCH AVAILABLE, THE UPDATER WILL DOWNLOAD THEM. THE TIMETABLE FOR THOSE PATCH RELEASES IS UP TO THE PUBLISHER DUE TO HOW THEIR PROTECTION SYSTEM WORKS.