OpenGen Questions & Bugs - Latest exe:25.10.27.1 ( 28-Oct-2025)

[none]

If this would apply to the player's units, i agree with Dimitris. It would be a big mistake and should be undone.

I second (third) that. What do you mean by "recon attachment"?

If it is the "additional spotting" attachment (the binoculars or dog head icon), I agree it shouldn't give any movement perks, to any player, human or not. After all it's just that, additional spotting (= commanding officer has got binoculars, that's all).
There is already a phased movement class, a phased movement special, and a phased movement leader, I think there are already enough options for phased movement.

[sympatyk]

The time frame for prototypes has been raised to 50 months now.

In fact, it works (you can enter) up to 60 months (as I requested).
However, for everything to be "perfect" --> is what I marked in red consistent with expectations?

True !!! ... Anyway, it should work as you wanted, as it only affects the texts.

Luckily, OG is not affected (it uses the time frame read from files) because I started moving AI3 to new files and cannot recompile OG until finished.

I'll fix the Suite glitch as soon as I finish converting all efiles having scenarios using old format to new .xscn format.

Thank you very much.

[Waldzios]

OpenGen 25.10.27.0 available with these changes.

• Recon attachment now makes any unit to move phased

Terrible idea.
There will be a lot of potential problems, across multiple units and classes.

[LuisGuzman]

Yes, I agree giving recon attachment phased movement, was a terrible idea
so I've uploaded 25.10.27.1 version rolling it back, which will be available tomorrow.

Also, I've finished updating all efiles using yet old SCN format to use the new XSCN which will be available in the Installer and all efile packages.

All the SCN files and MAP files have been removed and also most (maybe all) the CAM files and all campaigns are now using XCAM and XSCN files not needing any MAP file to convert on the fly while loading.
Actually, CAM files can be used at no risk as far as their scenarios are found as XSCN files.

[Dimitris GR]

Thanks is the least that i can say.
Estoy muy agradecida por todo lo que haces y nos das alegría.

[none]

A blast from the past...
Remember this?

OpenGen Version 25.02.26.0 ( 26-Feb-2025 ) released, fixing:

• [...]
• When upgrading, neither main equip nor transport data was shown matching the selected unit to update.
• [...]

Seems the Update Display Bug has partly come back (it's in September's OpenGen, I guess also in the later ones): In the Upgrade screen, when switching from one class of units to another, the unit name and the movement type icon changes, but not the picture and the data.
- But this time it does not happen for all units!

Selecting some of your units (consistently) changes everything as expected, but selecting others (consistently) only changes the name and the movement type icon...
I haven't found a logic about which units do and which don't, but there must be one, since it happens always with the same core units (independently of class).

[none]

Another bug...
My Open General (25.09.06.0) has gone crazy.
I have some free days and I'm making a small campaign. On starting the 3rd scenario one of the core units I hand out to the player didn't appear in the HQ menu, and when I quit Open General to check in Open Suite what the problem might be, I found a Notepad with the cryptic message:

Unit# 61 has a wrong position * skipped

What does that mean?

Counting the core units ported from the last scenario, there are 15 (core) + 6 (new) + 47 (AI) = 68 units in this scenario. But I can't really see which one was initially #61 (before being "skipped"), and the unit which doesn't appear in HQ is a new player core unit, so it's number can't be over 21. The only thing which makes some sense is that it was the last one I added in Open Suite when making the scenario, it was an afterthought.
All scenarios were made with Open Suite 25.09.06.0 BTW.

What does "wrong position" mean, and what does "skipped" mean? I have never seen this message before, in almost a hundred scenarios, and today I got it twice: The previous time was in the previous scenario, where I had apparently forgotten to deploy a bunch of AI reinforces (can't the AI deploy units? I thought it can?): Anyway deploying them made that issue disappear (at least I got no error message).

But in this scenario everyone is well deployed, I checked. So, is it a problem ported from the last scenario and getting worse with each scenario? Some corruption of the player unit list? I don't think so, it always complains about unit numbers in the AI range (last time it was 51, 52, 53, 54, 55), and AI units wouldn't be ported to the next scenario. The player had only 15 core units (in this scenario he gets another two).


Luis, does this type of message mean something specific?

Else I can try to send you the scenario and the previous savefile, but units will be wonky because it uses the new NOKorp2 E-File. (I can of course send you the whole thing too.)

-------------------------------------------------------
--- Edited: Explanation of the bug

I had a sudden inspiration, tested, and it proved right:
The issue is indeed undeployed units, even if they belong to the player and he is supposed to place them where ever he wants.

Open General 25.09.06.0 (and following?) does not like when there is 0/0 in "location". Even for units still in HQ.

All you need to do is to put some numbers in there and Open General is happy...
It's definitely a new bug, it didn't exist in the previous versions.