|
Post by generalvikus on Jun 16, 2023 17:59:22 GMT -6
I mentioned this in my post about the OOB editor not working, but I think it merits a separate thread. In this image, you can see four visible battle divisions, but in the OOB window there are nine. Five are stacked on top of and phased into one another underneath the northernmost visible division. I made sure in the division editor that everything was set up as it should be - in descending order, each division is cored to the next, from 10 down to 1. Incidentally, division 10 is supposed to be the fleet flag, but in this case it's division 8. Save attached. Attachments:RTWGame2.sta (91.01 KB)
|
|
|
Post by blarglol on Jun 16, 2023 20:57:32 GMT -6
I have seen this multiple times myself.
|
|
|
Post by Fredrik W on Jun 17, 2023 0:10:11 GMT -6
I mentioned this in my post about the OOB editor not working, but I think it merits a separate thread. In this image, you can see four visible battle divisions, but in the OOB window there are nine. Five are stacked on top of and phased into one another underneath the northernmost visible division. I made sure in the division editor that everything was set up as it should be - in descending order, each division is cored to the next, from 10 down to 1. Incidentally, division 10 is supposed to be the fleet flag, but in this case it's division 8. Save attached. Thanks. We need the entire zipped up save folder for a saved game, in this case the save folder Game2.
|
|
|
Post by blarglol on Jun 17, 2023 11:44:06 GMT -6
I have both a save and a pic here. You can clearly see three CAs 100% on top of each other, as well as the accompanying DDs.
Attachments:
|
|
|
Post by generalvikus on Jun 17, 2023 11:56:35 GMT -6
For me this happens in every fleet battle, no exceptions. It's definitely not fleet cruising formation - I disabled it and nothing changed. There definitely seems to be something funky going on with the OOB editor, too. It's not just that the ships are hopelessly scrambled - BCs mixed with predreadnoughts and so on. The same battle division - the 8th - has been my flag division in every single fleet battle, without fail. But it's supposed to be third in line; the 10th is supposed to be the flag division. Furthermore, in addition to the divisions spawning on top of one another, there are always a bunch of battle divisions cored to a single friendly division. At the start of every battle, it automatically reassigns all the cores to fix this, and then tries and fails to unscramble the resultant traffic jam, which usually leads to the formation of a black hole if I don't intervene. drive.google.com/file/d/11GgN1Z1ut6woaF0ty0JDS7wkNRwxGyS2/view?usp=sharing
|
|
|
Post by generalvikus on Jun 17, 2023 12:23:19 GMT -6
|
|
|
Post by asdfzxc922 on Jun 19, 2023 20:52:40 GMT -6
Related thread. There's at least three distinct bugs happening here: - The battle generator doesn't respect the roles the player assigns in the division editor.
- If one force has many divisions of the same type, then the battle generator seemingly runs out of places to put them and just sets all the remaining units to the same role. (Note how all the bugged divisions are grouped together at the bottom of the list in OP's screenshot. DesDivs 26 and 28, also at the bottom, are also suffering the same bug.)
- If two divisions do generate with the same role, they always spawn in exactly the same spot (sometimes one of the divisions is offset by a tiny amount, but it's only visible at near max zoom).
|
|
stele
New Member
Posts: 45
|
Post by stele on Jun 20, 2023 7:52:52 GMT -6
Multiple DD divisions in support spawn correctly in ofsetted parallel lines usually. It happens for core/independent and screens most often. And those multiple screens are assigned by battle generator as in OB editor only first div in line have screen assigned.
|
|
|
Post by blarglol on Jun 21, 2023 17:26:52 GMT -6
Related thread. There's at least three distinct bugs happening here: - The battle generator doesn't respect the roles the player assigns in the division editor.
- If one force has many divisions of the same type, then the battle generator seemingly runs out of places to put them and just sets all the remaining units to the same role. (Note how all the bugged divisions are grouped together at the bottom of the list in OP's screenshot. DesDivs 26 and 28, also at the bottom, are also suffering the same bug.)
- If two divisions do generate with the same role, they always spawn in exactly the same spot (sometimes one of the divisions is offset by a tiny amount, but it's only visible at near max zoom).
Lol thank you for finding my separate thread. I was like "I know I've talked about this elsewhere..."
|
|
|
Post by williammiller on Jun 22, 2023 8:39:58 GMT -6
The player divisions 'stay together' code has been adjusted for the next update so its behavior should be improved.
We are looking at the 'spawning-on-top' & OOB editor reports, thanks.
|
|
|
Post by arminpfano on Jun 22, 2023 9:22:49 GMT -6
I find the "spawning on top"-problem not really decisive, just a little annoying. After the first two or three minutes everything should be cleared. Please concentrate on important bugs.
|
|
|
Post by generalvikus on Jun 22, 2023 12:31:20 GMT -6
I find the "spawning on top"-problem not really decisive, just a little annoying. After the first two or three minutes everything should be cleared. Please concentrate on important bugs. In these early game battles it was always quite decisive, because contact was made immediately and long before the traffic jam or black hole resolved itself, and because my line was slower than the enemy's. As such, the head start it provided resulted in the enemy getting off more lightly than they should have on many occasions.
|
|
|
Post by blarglol on Oct 20, 2023 1:03:51 GMT -6
Still present in .25. B Divs 2 and 3 are on top of each other at battle start.
Just noticed they're each set to core the same division, which would explain it. Now I need to see if that is what I set them to or if it is erroneous.
Nope - it is an error. My division editor has BX 2 coring 1, and BX 3 coring 2, so I don't know why they are both set to follow 1...
Attachments:
|
|