Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[azura]

Korean maps in QMB are for JTW? In WAW, only blue sky! Does it go only for me ?
        Thanks in advance!

[Vampire_pilot]

I could say: logfile?

But that is very very old and has been reported many many times already, so easy to answer.

Korea quicks are JTW sensitive.
Not every QMB mission is compatible in every era.
There are other that only work in WAW.

[azura]

Thanks,always.

[western0221]

I've thought more smart user interface QMB for B.A.T. ......

Dec./2018's my topic is here ---- https://www.sas1946.com/main/index.php/topic,60074

"QMB(Pro) categorize and loading limit , what idea ? (especially on B.A.T.)"

Hi.

Especially in B.A.T. , not few QMB(Pro) missions are made with objects depending on the particular game era (Game Type in IL-2 Selector) , and such missions make loading errors in different game eras (Game Types) ..... "The objects in the mission are not registered in the current game era".
Many TechHelp questions have been posted about the issue.

This is noticed thing, but giving users confuse.

(snip)

I'm wondering how to collaborate with current "MissionProCombo PLUS" project.

[whistler]

Dec./2018's

That's the problem. Nobody is willing to work on QMB missions.

QMB Foundations are good, there is no need to alter the QMB GUI, at least, not yet. What is needed are dedicated and passionated QMB mission editors. QMB missions shouldn't be complex by any means: a few targets suffice (in my opinion!). We have Single Missions and Campaigns for elaborated scenarios.

Mission sets can be renamed in a breeze:

BAT_Stalingrad(RRR)_S > WAW_Stalingrad(RRR)_S
BAT_Stalingrad(RRR)_S > WAW_Stalingrad(RRR)_S
...

Spain_Center_spring > TGA_Spain_Center_spring
Spain_Center_summer > TGA_Spain_Center_summer
...

WWI_whatever > DOF_WWI_whatever
...

And we could still have, in example, BAT_WarOverItaly mission sets that include objects common to all modules. The BAT team can probably put together a list of objects common to all modules.

In the end, we would have:

BAT_MissionSet1
BAT_MissionSet2
BAT_MissionSet3
BAT_MissionSet4
...
DOF_MissionSet1
DOF_MissionSet2
DOF_MissionSet3
DOF_MissionSet4
...
TGA_MissionSet1
TGA_MissionSet2
TGA_MissionSet3
TGA_MissionSet4
...
JTW_MissionSet1
JTW_MissionSet2
JTW_MissionSet3
JTW_MissionSet4
...
WAW_MissionSet1
WAW_MissionSet2
WAW_MissionSet3
WAW_MissionSet4

That's the easiest part. It can be done in 15 minutes.

The hardest part comes next: someone has to go through all missions and make sure all are built up to module X standards.

[Knochenlutscher]

Someone put whole A4 spreadsheets into a BAT QMB property, not knowing these properties must be the length of a small line,
minimalistic with short iNfo for HUD. QMB Info HUD is not for Campaign briefings style, too long.
These Properties Info HUD where for the Special Missions,
Torpedos, Levelbombing, Mistel, Carrier Ops etc.
outside the stock QMB targets parameter. Your new Mission Pro still handles these Missions, but it can't read the short properties anymore,
as the Hud Info ceased. Bring it back and it will pay out. That is a shortcoming that I see, as the space of the Info
Hud is unused and people could complain if remaining Special Missions are in, a Armour Mission that is Levelbombing.
You can have both, strict and Special QMB.

The rest is carefull rework, lots of testing to get QMB on the feet again.

[whistler]

Excuse me Knochenlutscher but I am not following. I am not sure about what you are trying to say.

QMB still reads .properties files and missions can have any name you want, if you want.

[...] these properties must be the length of a small line, minimalistic with short iNfo for HUD. QMB Info HUD is not for Campaign briefings style, too long.

This is a personal preference, isn't it? Nobody is forcing you to do anything in any particular way.

[Knochenlutscher]

No, I read about it being deleted, haven't seen this small Button yet.
That is good News it's still there.

I need to get used to the new Menu, but also find out it's boundaries, capabillities.
I'm still too much into the workflow of the old, have to relearn a bit.