JaguarUSF

The AI for quick battles is scripted very generally, since the designer doesn't know what units will be involved: it's basically a "set up here" and a "move here" order and that's it.

I'm glad you enjoyed my scenario (it gives me a warm, fuzzy feeling inside). FYI, I put that together in about 45 minutes using the scenario editor. Now, play as Red and see if you can take out those dirty, stinking Americans.

Indeed. Now I'm glad I didn't mention the lack of a tutorial in my review.

The author is usually on the second page of the briefing (if you click "next" right above the OK button). I would think that all of the scenarios that don't specifically state "play as blue only" will work fine for multiplayer.

Use the move command and set the waypoint to somewhere in the blue box.

No, not while my greatest nemesis still provides our customers with free light, heat and energy. I call this enemy...the sun.

I got the final 1.01 install and I can confirm that I am getting the teleportation bug again. Weird since it was fixed in one of the beta versions of the 1.01 patch.

I've found that disabling Antialiasing, anisotropic filtering, and vertical sync in the game AND in the nVidia control panel improves performance drastically.

The AI plan looks correct, so it's obviously not MY fault Probably just the tactical AI. It takes some time to "get going" on its orders (like a minute or two), and in a small scenario such as that one it's a bit more obvious.

Yep, Game Files\Scenarios

Here you go: http://www.battlefront.com/cgi-bin/bbs/ultimatebb.cgi?ubb=get_topic&f=52&t=001833

Please to enjoy eight scenarios I designed while playing the preview version of CMSF that were too crappy to make it into the release version of the game. They are completely playable from both sides and supposedly balanced. Here is the link: http://home.comcast.net/~jaguarusf/James_Allen_Scenarios_of_Doom.zip Enjoy!

Yep. Fully functioning and playable from either side, although not up to the same quality standards as the ones that shipped with the game. You'll notice a lot of the maps were included as quick battles, though, but I'd like to upload them as well.

I hear that James Allen guy r0x0rz. Notice the objectives are hidden and different for each side. Pretty sneaky!

For fun and profit. Look in the Quick Battle Maps directory (in Game Files). Those are the combinations you are allowed.

I was getting teleportation while I did my review, and they did a fix in 1.01 that solved it. From the looks of it, I think the culprit is the Athlon 64 X2 processor: that is the commonality (I also have an Athlon 64 X2). I haven't played a non-beta version of 1.01 yet so I don't know if I still have the lockups.

If there isn't a map with the settings you requested, it goes back to the main menu. You can see all of the allowed combinations of type (meeting engagement, probe, assault, etc) and environment (hilly, town, etc) in the QuickBattles directory.

If there isn't a map with the settings you requested, it goes back to the main menu. You can see all of the allowed combinations of type (meeting engagement, probe, assault, etc) and environment (hilly, town, etc) in the QuickBattles directory.

Which version of the game are you running with the teleporting units?

All of my missions are balanced and intended for multiplayer; they can be won from either side. I also like to use different objectives for each side...keeps things FRESH.

I have eight scenarios that were not included in the game (or were used for Quick Battle Maps); where would you suggest I upload them for general consumption? Is there an appropriate fan site?

They said it to me when I was reviewing the game.

Yes. This is a problem I discoverd while reviewing the game, and I believe a fix is being made for 1.02.

nVidia drivers are bad...Battlefront is apparently working on a fix planned for 1.02.

I did say "like" the nVidia problem; he does have a dual core like I do which made me suspicious. The problem I experienced, more specifically, is when models require more than one pass to render: my card craps out, and the fix is optimizing the models. Or so I was told.