I second (third) that. What do you mean by "recon attachment"?
LuisGuzman wrote: ↑2025-10-28 11:46, TuesdayTrue !!! ... 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.
Terrible idea.LuisGuzman wrote: ↑2025-10-28 08:32, Tuesday OpenGen 25.10.27.0 available with these changes.
- Recon attachment now makes any unit to move phased
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.LuisGuzman wrote: ↑2025-02-27 06:46, ThursdayOpenGen 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.
- [...]
What does that mean?Open General wrote:Unit# 61 has a wrong position * skipped
Indeed, that was something I do not even remember to have done!, but yest I commented out a line avoiding that.Open General 25.09.06.0 (and following?) does not like when there is 0/0 in "location". Even for units still in HQ.
Beware, it breaks all and every scenario where any of the players gets units to deploy...
Sorry, had no time to look at this, because this update screen is hard to debug and this kind of issues not being clearly able to replicate require a good amount of time, that I lack right now.none wrote: ↑2025-10-31 16:54, Friday Some news about the update screen regression: It apparently only happens when there are many core units (which is probably why nobody else spotted it). I'm working right now on a small and quick campaign with <20 core units, and everything works as expected so far.
none wrote: ↑2025-11-03 15:12, Monday Bug: Open General (25.10.27.1) doesn't like some Leaders!
I made a test scenario, or rather a mini-campaign: In the first scenario just move to the VH to win. Now in the second scenario, go to Upgrade, and try changing both units' transports to anything else.Here is the test scenario. (NOKorp2, but those units haven't changed so it will work just fine with the old NOKorp)
- On the infantry unit with the 01/21 (Tenacious Defense/Infiltration Tactics) leader, OG will insist on changing its leader
- On an identical infantry unit, but with a 01/12 (Tenacious Defense/First Strike) leader, OG won't touch the leader, as expected...
a OG bug, maybe a danger design.LuisGuzman wrote: ↑2025-11-05 19:44, Wednesday have an Infiltration Tactics leader which is not compatible with Pioneer attribute.
I see, thanks. Could you eventually make that "incompatible leader" message a little clearer? The current message is a little confusing... How do you suggest?
)
IIRC no, if you let the game decide, it will chose randomly among all the units the player could get at that time period.
No (unless I misunderstood your question), but what you can do is to tell the trigger precisely which unit the player should get. That's what I usually do, scenario-based: If the player captures a tank factory, he might get a captured enemy tank (like a "Panzerkampfwagen T-34 747(r)) (or an enemy artillery unit, complete with a fitting transport, or some such). It's also more logical than getting all of a sudden a freebie out of nowhere, IMHO.
Thanks for the answer! I see it is not possible to curate the protos raised by trigger hex.none wrote: ↑2026-01-04 16:35, SundayIIRC no, if you let the game decide, it will chose randomly among all the units the player could get at that time period.
No (unless I misunderstood your question), but what you can do is to tell the trigger precisely which unit the player should get. That's what I usually do, scenario-based: If the player captures a tank factory, he might get a captured enemy tank (like a "Panzerkampfwagen T-34 747(r)) (or an enemy artillery unit, complete with a fitting transport, or some such). It's also more logical than getting all of a sudden a freebie out of nowhere, IMHO.
I'd prefer no planes at all. I think that would be too dangerous: Once in a while chance might do it right, but the other times the player will find himself with 10 AA units, one light tank and 3 bridging units... It is just a fun option I want to add. Just for fun, really. Without the planes there are still ~60 units available as protos in a 12 months time frame and even odd armies look good and playable. Only the ~30 plane protos are a bit annoying because somehow the player always gets so many of them. At least when I test it.none wrote: ↑2026-01-04 18:29, Sunday
Seriously, a viable army needs to be well-balanced, so unless you can point the game at what the results should be and restrict the choices, a 14-random-units army will be unplayable more often than not...
Hmm. That kind of makes sense.
If that true it is a huge error! The higher you are, the farther/better you see, and as soon as there were any flying machines (balloons, then planes), they were immediately used by the army for reconnaissance.
Randowe is right, recon class is a ground class, regardless you set as using airspace and air movement.none wrote: ↑2026-01-11 16:50, SundayHmm. That kind of makes sense.
Though I'd like Luis' opinion on this. Because:
If that true it is a huge error! The higher you are, the farther/better you see, and as soon as there were any flying machines (balloons, then planes), they were immediately used by the army for reconnaissance.
In WWII there were photographic reconnaissance planes (usually unarmed), and "armed reconnaissance" airplanes which were flying search & destroy missions. So, just to take German planes, there isn't one major type which didn't also get a reconnaissance variant, from the Bf 109 fighter to the Ju 88 bomber, not to mention the dedicated recon planes like the Fw 189 "Uhu" for instance.
