Made some good progress today. I have six different mission types each with their own routing. For scouts I have patrol, offensive, and CAP. For two seaters I have bombing, recon, and artillery spot. I adjusted the lengths to try and avoid overly long missions for the player. I also corrected some routing issues.

Seat of the pants ETA is the end of the month for the first release version.

Ming

Still plugging away. I've been correcting bugs, doing squadron edits, and working with missions. It's shaping up. The big ting now is to refine mission pathing. The end of the month is still looking reasonable.

If you have any questions that you think I may be able to answer, feel free to send a PM my way.


Look forward to your results.

Hello

Interested in this new Campaign mode of course (and made by an unofficial player, not tied to NEOQB, bravo!), and also interested in the reports forms posted on page 3.
I've downloaded the USAS and RFC report forms, anyone knows if and where can I find reports froms for French Aeronautique Militaire?
These forms rocks, we start to use it after some historical coops, it's really fun to report your victorie, events...

Pat, all this sounds very exciting. Please keep going in the knowledge that your efforts are much appreciated. Looking forward to the results!

Cheers,

RD.

Exciting stuff. And thanks for keeping us posted on developments. It is such a rarity theses days.

Has there been any comments from Neoqb re a mission results output file?

Not wanting to spoil the air of expectation in here but I don't see how entering all the outcomes for your flight is really a goer. I'd be able to keep my own tally but as far as the rest of my flight goes I don't see how I'm supposed to know how they performed, or even if they're still alive tbh.

Indeed. I've been also thinking about this. One way, imperfect but still helpful, is to attached a subtitle for every plane in game, like this: the subtitle should be hooked to the OnKilled message for every plane, and each subtitle should mention the name of the pilot (which you have it because the campaign tracks it). When a pilot is killed, you have much bigger chances to see that if a message appears on screen stating that "Killroy was killed". At least you know that and have time to note it, as a minimum base.

Yes, this is no replacement for a mission result file. Ideally, the mission format should allow for custom data logging to a file, which can be used as a result file. So you log only what you want.

S!

Simply breathtaking in scope.

Wow.

The names are already fairly detailed. For the player squadron the name of each plane entity is the pilot's name. For non-player flights it is the type and squadron name (new as of last night so testers won't see this yet). I can look into on-killed.

Inside the campaign code I do an assessment of whether a squadron mate was killed or not killed. You just tell me that a particular pilot was shot down. Obviously getting it all from a results file is better, but it works for now.

Now - back to "on message" - we have this:
OnMsg
{
Type = 9;
CmdId = 0;
TarId = 7;
}

Type = 9 is onKilled
TarId = 7 is the index value of the aircraft's MCU TR entity
What is CmdId? What are the possible values and what will they do?

aloha Patrick. good to see you working with OnMessages.
per my current understanding CmdId is Command ID. possible values are the ID #s of commands.





from neoqb MissionBuilder lesson3:

After the mission begins, the Timer by means of TL will execute command “Take off” for our planes. Aircraft will take off, but where should they go? In a takeoff procedure we have used Message link for the first time (See Lesson 2). With this message (Take off) group of our planes will report to the script that the take off command is successfully accomplished and now Script should activate the first CP, i.e. where to go. This procedure is a compulsory for take off it should be remembered ones and for all.


hope that helps.

Thanks again. My stuff is all air start so I have not run into that yet. If I had tried ground start I would have failed miserably. I did read the lessons but like any other learning curve I don't pick it up all at once. I do want to get the player started on the ground, so I will have to remember that.

This stuff is great for so many reasons, but top of the list is it gives players of different stripes the options they desire.

About a zillion years ago (in Internet time), back when RoF was KotS, a bunch of us had a big conversation about what a campaign should be. It was split between the detailed sort of genuis Patrick is putting together and the more sterile sort of campaign that comes stock with the sim (okay, maybe not quite as stripped down, but not much more fleshed out), with lots of quality points on both sides (and enough heated words to keep the coffee hot). It's no secret that I'm a "down and dirty" sort of player, but that doesn't mean I don't appreciate those who want a great deal more detail.

The one thing we agreed on, however, was that players should have options.

I do believe that the entire community owes Patrick a huge thank you; it's folks like him that make simulations more than just fun; they make them a real enjoyment.

I'd make this thread a sticky, but everyone seems to ignore sticky threads.

So a nice little bump to the top instead.

I think I've read above in this topic that you need some generic skins for squadrons.

Here you can find 3 generic skins for USAS Spads:
- one generic skin for an American Spad
- one generic skin for a Spad of 94th Aero Squadron
- one generic skin for a Spad of 27th Aero Squadron.

All these skins have no number or personal insignia, just squadron insignias.

http://www.megaupload.com/?d=O5W43JLH

Barring anything unexpected I will release version 1 when the Camel and DRI come out. I have Camel and DRi squadrons in the game but they are currently rerouted to the SE5a and Albatros. When the DRI and Camel come out these squadrons will really fly Camels and DRIs. Seems like a good time.