0.73b1 test build

Post by **ILMTitan** » 08 Sep 2006, 19:55

KDR_11k wrote:I think Fight and Patrol makes the units suspend their movement, mark their current spot as their return point, destroy the enemy, then return to their marked spot and continue moving from there. Maybe setting them to Roam changes that?

Essentially, yes. I meant it to keep units from being pulled off their path arbitrary distances by a succession of targets. (Roam did not change this, but that is a good idea for the future). Something seems to have changed since then, however, and it seems that units can be pulled arbitrary distances anyhow. I may try make the behavior act more intuitively this weekend, (hopefully) before .73 comes out.

Rafal99 · Post by **Rafal99** » 08 Sep 2006, 22:04

Lines drawn by AIs are borked.

esteroth12 · Post by **esteroth12** » 09 Sep 2006, 00:28

Caydr wrote:
ofc, this is only if Mars' and SmallDivide's makers want to remake them

did NoiZe make them both?
I'm usually wrong, but I really don't think Noize made those. Also, you can't just convert a map to SM3, it'd have to be remade from scratch, unless an SY still has the heightmap they used lying around somewhere.

thats why i used remake, not convert

SwiftSpear · Post by **SwiftSpear** » 09 Sep 2006, 12:10

AI's draw lines? Most spring releases break AI's somehow, usually it's a problem AI side, not spring side.

Rafal99 · Post by **Rafal99** » 09 Sep 2006, 13:52

Yes, AI's can draw lines. They are mostly used for debugging purposes.
I have my own AI project and there is no way to break lines to make them look like this.
I am sure it is a Spring problem, it happens with SVN revisions since the changes in texture system.

Soulless1 · Post by **Soulless1** » 09 Sep 2006, 15:12

Caydr wrote:Eh, er, where do I get that?

think it's bundled with NTai atm - called MapAI or something

KDR_11k · Post by **KDR_11k** » 09 Sep 2006, 15:53

I'm getting a completely weird extractor range display in 2097:

Sometimes you can even see parts of extractor radiuses that aren't in your LOS.

Hunch: The changed LOS resolution in the sensors.tdf isn't used correctly by the check if the extractor range is within view. Sometimes I'm seeing weird patterns of seen and unseen radius texels on radiuses that are in the southern ~3/4ths of the map, suggesting that it's using "junk" data for that, i.e. data exceeding the LOS array.

bobthedinosaur · Post by **bobthedinosaur** » 09 Sep 2006, 22:59

hmmm been trying out some of the new tags, not too many seem to work for me and the change log isnt ver helpful. there are no examples, and some lack any description on what they do. would any one like to post what they have found with new the fbi, tdf tags?

Tobi · Post by **Tobi** » 09 Sep 2006, 23:17

KDR_11k wrote: [...]
Sometimes you can even see parts of extractor radiuses that aren't in your LOS.

Hunch: The changed LOS resolution in the sensors.tdf isn't used correctly by the check if the extractor range is within view. Sometimes I'm seeing weird patterns of seen and unseen radius texels on radiuses that are in the southern ~3/4ths of the map, suggesting that it's using "junk" data for that, i.e. data exceeding the LOS array.

Which mod is this and what are the contents of sensors.tdf?
If it's unreleased I'd prefer if you could PM me a link to the mod to reproduce the bug.

KDR_11k · Post by **KDR_11k** » 09 Sep 2006, 23:49

It's the GINTA techdemo here. The sensors.tdf is set to 4x size for LOS and aerial LOS. It should also demonstrate the "dead units remain as targets until Killed returns" bug I've posted in Mantis.

Soulless1 · Post by **Soulless1** » 10 Sep 2006, 01:28

btw on a *kind of similar* note, has anyone found a way to fix cloaked mexes still leaving an extractor radius yet?

Post by **ILMTitan** » 10 Sep 2006, 10:32

Caydr wrote: And it behaves strangely. I told group A to "fight" to a location on the other side of group B. Group A comes across group B, kills it, then returns to their start location, THEN proceeds to the location I told them to "fight" to. Might've already been fixed, I'm not sure what build I was using at the time.

Patch up. May (hopefully) be small enough to be in .73. Units now move to the closest point on the old path, as opposed to their original position.
http://taspring.clan-sy.com/mantis/view.php?id=292

Soulless1 · Post by **Soulless1** » 10 Sep 2006, 14:57

ILMTitan wrote: Units now move to the closest point on the old path, as opposed to their original position.

schweet - good thinking

Rafal99 · Post by **Rafal99** » 11 Sep 2006, 00:53

SVN log wrote:2129 / tvo 23 hours * BUGFIX: fix AI line drawing (according to how it was before r1625)

Great, AI lines now look like they should!

Thanks Tobi !!!

Caydr · Post by **Caydr** » 12 Sep 2006, 00:05

Someone make me a build up to at least rev 2136 please?

KDR_11k · Post by **KDR_11k** » 12 Sep 2006, 07:25

Code: Select all

build\tools\unitsync\unitsync.o(.text+0xaa):unitsync.cpp: undefined reference to
 `ConfigHandler::Deallocate()'
build\tools\unitsync\unitsync.o(.text+0xcb):unitsync.cpp: undefined reference to
 `ConfigHandler::Deallocate()'
rts\System\Platform\FileSystem.o(.text+0x43c):FileSystem.cpp: undefined referenc
e to `ConfigHandler::GetInstance()'

Tobi · Post by **Tobi** » 12 Sep 2006, 11:40

Add ConfigHandler.{cpp,h} & RegHandler.{cpp,h} to the project.

KDR_11k · Post by **KDR_11k** » 12 Sep 2006, 11:57

Project? You mean add it to the SConscript file somewhere?

Tobi · Post by **Tobi** » 12 Sep 2006, 13:26

Bah, guess MinGW port is bitrotting because I didn't look at it for three weeks...

KDR_11k · Post by **KDR_11k** » 12 Sep 2006, 15:31

Hm, adding the lines works but the Assertion Failed problem persists.

Spring RTS Engine

0.73b1 test build