Jump to content

1.2.6 Release...


ClaytoniousRex

Recommended Posts

...is now available via Update. You should be prompted to update automatically the next time you run DropTeam.

Changes in 1.2.6:

</font>

  • Reduced network bandwidth</font>
  • New scenario "The Dam" by Toby Haynes</font>
  • Linux version now allows you to explicitly select a sound system on the Settings tab (pull down the "Sound Driver" combo box to try different backends)</font>
  • Modder support (armed aircraft, collapsible object tags)</font>
  • Speed optimizations</font>
  • More (minor) bot improvements</font>

Link to comment
Share on other sites

Sadly, I'm staring at memory corruption error message right now. After a bit of fiddling (pointing the LD_LIBRARY_PATH at my 32bit libraries) and putting the DropTeam libraries first in the list of searched locations, I'm still crashing when starting a scenario. It gets through the scenario setup and crashes within a few seconds of displaying the landscape for the first time. The landscape is all messed up on screen too - large sections are missing, making it look like something from Tron. Here's the last lines from a standalone game.

</font><blockquote>code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">...

COB: Loading texture >../data/gs-mapBurned.dds<

GUIMANAGER: Preloading objects complete

Warning: detected OpenGL error 'invalid operation' after RenderBin::draw(,)

PROFANITYMANAGER: Loading ../data/Profanity.xml

GUIMANAGER: STATUS MSG: Nexus6a has joined the Water team

Warning: detected OpenGL error 'invalid operation' after RenderBin::draw(,)</pre>

Link to comment
Share on other sites

I'm currently at Ubuntu 6.10 AMD64 - maybe I'll try to upgrade to 7.04 if it's working for Poesel.
I have been seeing a lot of posts regarding Upgrades to 7.04 while running on AMD64 systems Toby! (Repo errors)

You might want to check out the ubuntuforums.org before doing anything to your /etc/apt/sources.list.

Link to comment
Share on other sites

  • 2 weeks later...

For the record, there were two things that caused my troubles with 1.2.6. Firstly, I seemed to pick up unneeded libraries from somewhere - moving all the libraries out of Dropteam/lib and tweaking version.ini to force an update worked for that.

The second part of the puzzle was the new OpenAL libraries seemed to cause problems: No ALC context was the error. Replacing the Dropteam OpenAL libraries with the standard Ubuntu ones solved that issue.

Link to comment
Share on other sites

I've more or less had none of these problems, but I've had one strange glitch. One bot wil suddenly begin talking, first saying something along the lines of "I'm attacking" followed by "I'll be your escort." But then it begins to repeat the two, at the insane speeds only a computer can manage, blurring its speech until it is some strange vibrating noise. Then, I give the bot orders, and another begins the process. Anyone else have this problem?

Link to comment
Share on other sites

Personally, I turn the bot voices off becuse they disrupt voice comms to much for my liking. The strange switch of orders back and forth might help explain the annoying habit the bots have of grouping together in some far off corner off the map and basically following each other nowhere.

Link to comment
Share on other sites

I have noticed that the dropships are much easier to shoot down than they used to be - unless I micro-manage the bots they tend to get shot down alot and I run out of drop ships.

One time after I ran out of dropships, I tried inserting a Viper, but I could not insert it outside of the deployment zone. I think it should be able to be inserted outside the deployment zone - being able to fly itself. I could insert it in the deployment zone, but then it would appear at ground level and quickly get immobilized (ie by colliding with the ground and flipping over).

Link to comment
Share on other sites

I think it's an a or b solution there.

A. Deployable anywhere. This makes sense realistically. However, should gunships ever make their way into the main game, it could throw a wrench into game balance if a gunship/bomber could drop behind enemy lines. (Once again, realism. It would make AA coverage over an advance all the more crucial)

B. Deployable only in drop zones, as was mentioned, just make sure they deploy higher, instead of at ground level.

I personally, from a realisim perspective, prefer option A, but we need to see how gunships impact the battlefield on CZ first, I think.

Link to comment
Share on other sites

Another thing:

Bane and me played yesterday together and I wanted to save our bots from dropping into Nexus & jby ion barrage. So I promoted myself and pressed 'Halt all drops' which to my (and Banes!) surprise also stopped Bane from dropping.

That should really be only an order for bots and a recommandation for humans. All other orders work the same anyway.

Link to comment
Share on other sites

  • 5 weeks later...
×
×
  • Create New...