Custom Map #3216: VPAC Position Updated. By: Vertu

[AutoPost]

This topic is for discussion of map #3216: VPAC Position Updated


Author: Vertu
Size: 180x180

[havoctheory]

With this map, as well with almost every VPAC map, I have an issue when after map reload, every existing Creeper unit becomes unselectable. The units (e.g. emitter bases) still function, I can see their output at the tooltip, the newly created units (if I have any power units left) work fine, but I cannot select and interact with every unit what existed at the map save. It is a major issue because I cannot move emitters nor change fieldgen directions etc. Basically, it is the game over. Re-loading the same save file again does not help with the issue, the save seems to be corrupted forever.

[Vertu]

With this map, as well with almost every VPAC map, I have an issue when after map reload, every existing Creeper unit becomes unselectable. The units (e.g. emitter bases) still function, I can see their output at the tooltip, the newly created units (if I have any power units left) work fine, but I cannot select and interact with every unit what existed at the map save. It is a major issue because I cannot move emitters nor change fieldgen directions etc. Basically, it is the game over. Re-loading the same save file again does not help with the issue, the save seems to be corrupted forever.

I have no idea how you encounter this.
I can not solve it if I can not witness the problem in action myself. Everything works flawlessly on reload and there is never an instance of being unable to select the VPAC buildings. Not many things happen on Gameload and selectability is not one of them.

What ever you did to cause this is requires an unusual setup to cause it. Something deliberate like placing buildings before unpausing so 0 frames pass, reloading the save, and something happens because why the hell would you save and reload from there?
If that is somehow what you did and I guessed it perfectly, I am not fixing it unless I randomly do so. It is more your fault than mine in that case but only if my example was a correct guess.

If your problem was any way common, A LOT more people would tell me of it.

[Karsten75]

Both of the participants in this thread may want to verify that they are on the latest game build. 2.3.3 IIRC - it appears below the credits box on the main screen.

[havoctheory]

I have no idea how you encounter this.
I can not solve it if I can not witness the problem in action myself. Everything works flawlessly on reload and there is never an instance of being unable to select the VPAC buildings. Not many things happen on Gameload and selectability is not one of them.

What ever you did to cause this is requires an unusual setup to cause it. Something deliberate like placing buildings before unpausing so 0 frames pass, reloading the save, and something happens because why the hell would you save and reload from there?
If that is somehow what you did and I guessed it perfectly, I am not fixing it unless I randomly do so. It is more your fault than mine in that case but only if my example was a correct guess.

If your problem was any way common, A LOT more people would tell me of it.

No and no,  I am not doing anything peculiar, and this issue never occurred in non-V PACs I use. I just played the usual way, and after the reload, all the existing VPAC units became unclickable. My CW4 is of the latest version available at Steam at the time of writing (2.3.3), it was the first thing I checked after encountering the bug. Are the saves transferrable between the systems?