Page 1 of 1

SP's in Editor

Posted: Thu Sep 16, 2010 4:32 am
by sPzAbt653
Using .178 on the XP and '98 OS's.

In the editor, supply points in enemy owned hexes cannot be seen anymore. The scenario dump still lists them, but they are not visible on the map. When waving the cursor over a hex that has one, it still prompts you to place one, instead of removing it. Placing one doesn't seem to place one. Playing the scenario, the supply points do appear when the hex ownership is converted. [:(]

RE: SP's in Editor

Posted: Sun Sep 19, 2010 9:12 pm
by sPzAbt653
For example, I snipped a piece of map from the editor that I know has friendly [red] supply points in enemy territory and they are not visible. The inset is a cut from the scenario dump showing the supply point locations. For the friendly hexes at 26,30 and 28,30 the supply points are visible, but for the ones in enemy territory they are not visible.

If I put the mouse on the supply point at 26,30 or 28,30, the dialogue at the bottom says 'right click to remove supply point', but right clicking brings up the box for assigning a value. Assigning a value of '0' removes it, and it can be replaced by assigning a positive value. But moving to 27,30 and right clicking to place a supply point and asigning a value seems to have no effect.

Image

RE: SP's in Editor

Posted: Mon Sep 20, 2010 11:46 am
by Curtis Lemay
Although you could use "Toggle Ownership" to reveal the SP, this has been fixed in 3.4.0.186.

RE: SP's in Editor

Posted: Mon Sep 20, 2010 10:05 pm
by BigDuke66
.186? Another Alpha?

RE: SP's in Editor

Posted: Tue Sep 21, 2010 11:15 pm
by ralphtricky
ORIGINAL: BigDuke66

.186? Another Alpha?
An internal build number. I keep every change so that I can trace back and pint the finger at myself[:-]. It's useful for seeing why I did such a bone headed thing so I can try to make a different mistake next time.

The release build should be either 187 or 190. It depends on the timing, I made a 190 with a minor change, but unless we've got time to test it, we'll go with 187. Unless I discover some other boneheaded mistakes, of course.

RE: SP's in Editor

Posted: Tue Sep 21, 2010 11:17 pm
by ralphtricky
A change can be one or many updates, but is generally one feature, or bug fix (possibly for a feature that was added.) So I've made 190 distinct changes from 3.3 to 3.4. Crazy, isn't it?

RE: SP's in Editor

Posted: Wed Sep 22, 2010 9:48 am
by Sker
ORIGINAL: ralphtrick

An internal build number. I keep every change so that I can trace back and pint the finger at myself[:-]. It's useful for seeing why I did such a bone headed thing so I can try to make a different mistake next time.

The release build should be either 187 or 190. It depends on the timing, I made a 190 with a minor change, but unless we've got time to test it, we'll go with 187. Unless I discover some other boneheaded mistakes, of course.

So we can expect the official release to come out very soon?

Anyway I think it's quite normal having many changes in such a wide project like this 3.4 patch, the more you change from the original game the more bug you will have to fix.
If any minor change will be cut from the patch it can be included in the next one