busdriver

Actually he didn’t post it, he sent it to me explaining he hadn’t tested it since he didn’t have BH&H2. I included the beta label.

Observation: Currently the "Mission Hour" feature only allows you to delay the mission start time by up to three hours. When squadron activity is low (one player sortie per day) this frequently means you cannot fly an afternoon mission. Advancing to the next day or week when flying activity is low does not change this limitation. When flying activity is high, you must still fly in the morning in order to fly in the afternoon (you might get a second morning sortie). It appears to me that the player is required to fly in the morning. At least this has been my experience with a handful of short British & French careers in 1916. My Observer/Gunners hate flying before lunch, mostly they're useful just prior to afternoon tea. Suggestion: Modify the "Mission Hour" to permit delaying the mission time well into the afternoon or evening. This would allow a player the flexibility to fly either in the morning or afternoon. Squiffy, Geoffery and Basil thank you in advance.

LOL, thought it was my imagination. Cruising back home, hear the occasional sound of fabric ripping with no other airplanes around. The sound of crashing airplanes is equally perplexing, causing me to pan around looking for the poor bast@rd. By watching the rest of B Flight in the landing circuit (whilst I’m sitting with my engine off), I noticed the sound of their engines goes away when they’re beyond 1.5 miles (just when they turn base leg).

I’ve noticed this in the Strutter and Bristol F2B, but that is the limit of my game play thus far.

Just installed CCFM, playing BH&H2

Suggestion: When B Flight is "in transit" back to base, please program an enroute descent so the formation arrives over our airfield at a nominal pattern altitude of 2000 feet (or 600 meters) rather than arriving at their patrol altitude. My observer is a bit of whinger, and he's tired of freezing his bollocks. He tells me that the nominal lapse rate is about 2C per thousand feet (1.5C saturated lapse rate and 3C dry lapse rate) so we would be much warmer and save 10 to 15 minutes getting to the bar. Think of it as a win-win.

That oddity of the rudder pedals axis defaulting to the throttle is something I experienced as well. Glad you got it sussed out.

@Graham1964 I use the Logitech X-56 throttle and stick combo. I had a similar experience yesterday (patched to 1.04). Below are the WOFFKeys settings for my throttle. You might notice that I have NOTHING bound to the Z Axis, which on the X-56 is the thumbwheel/rotary axis on top of the right-hand throttle lever. In other sims I use that to control propellor pitch (rpm). Typically I use the auto-pilot until the formation is joined up. Upon disconnecting auto-pilot, I was unable to get the power above 50%. Both throttle levers were full forward, but the rest of the formation was pulling away. I hit the F5 key to see that power was maxed out at 50%. I could reduce to 0% so I thought the sim was giving me a random engine failure and I headed back to base to land. While I was headed back I started fumbling with buttons and switches thinking perhaps I had porked my WOFFKeys programming (that I had tested pretty well). Turns out that the Z-Axis was acting not as a throttle but more like a limiter switch. Meaning when I turned it full anti-clockwise I got 100% power and full clockwise I got 0% power with the throttles full forward. However, with the throttles full aft (Idle) cycling the rotary did NOTHING. I suspect I had the Z-Axis at the max value of 10000 (full anti-clockwise) when I initially programmed WOFFKeys. But I cannot be sure. I went back and set the Z axis to the mid-range detent (that 4961 value cycles to 5000) then bound the Throttle to my throttle lever (Y Axis). Testing so far shows the Z Axis rotary is not affecting the power setting at all. Good luck.

I am merely confirming @veltjens's observation. My Caudron G4 career as Corporal Test Dummy is complete. Cheers

More testing and thus far I'm only encountering this extreme takeoff interval with the Caudron G4. Latest test career with C 4 at Pierrefonds (Marne) in Jan 1916 then to Lemmes (Verdun) advancing time a week or month after each mission. Generally speaking, I'm observing B Flight Lead typically starts his takeoff roll 1:45 to 3:00 after starting engines. I did see one immediate takeoff when the activity switched to "Taking Off" at 25 seconds after engine start. The rest of B Flight delays about another minute before somebody rolls. I observed only one mission where all of B Flight and A Flight rolled with minimum delay. Often A Flight doesn't takeoff until we are long gone. The first mission after moving to Lemmes, B Flight Lead rolled promptly at 30 seconds and all others delayed until 8:30. By then Lead was over 5 miles away "in transit" to the front lines. Perhaps it means nothing, but viewing from the cockpit my throttles were rapidly slamming back and forth as we waited. When number 2 rolled we all rolled with minimum interval. I'm concurrently playing a Strutter career (Summer of 1916) and Bristol F2B career (Spring 1917) and have not seen this degree of persistent takeoff delay.

That's an excellent point. I don't use Mods.

I can confirm your observation. Well to the point of waiting 5 minutes and not seeing some AI nor my own crate (full autopilot mode just for testing) takeoff. I'm the green arrow. However, I've not noticed this in my RFC two-seater careers. I do see some random takeoff order where the Leader is not the first one in B Flight to takeoff.

It's that bit of time after forming up is complete and as @Baldric says, the formation is climbing up to cruise altitude. Once the "forming up" portion is complete you can (even as a mere wingman) use [Shift] + [ W ] to send the formation to a down range waypoint and they will climb enroute. I do that ALL.THE.TIME.

Well, for me it allows me to edit the mission or claim narrative. For example, instead of the generic mission description of Patrol Behind Friendly Lines, I changed to read something more descriptive. And I edited the narrative to describe in a bit more detail.

Our hero JJJ65 has given permission to test at will. It works for me. WOFF BH&H2 Pilot Log Editor.rar

You're quite right, our friend Jara is tremendously talented. I love this utility.

That's all I'm doing for now. Letting my observer score the occasional airplane victory while I put bombs on target and once in a blue moon flame a balloon.

@trotski00 without any knowledge of the specific unit that displays the “aircraft not available yet” message, is it possible (probable) the date of such message is prior to the unit becoming operational? Or possibly on the date of such message that the unit was equipped with an aircraft not included in the sim?

I understand about airfields close together. I just had a debrief screen showing that I landed back at Fienvillers/Candas (70 Sqn's base) when I landed at Chipilly. Perhaps there is a way for the debrief screen to simply show Landed without an airfield. This would prevent the shifting down of status info. Perhaps make the debrief screen less complicated.

Offered as an observation NOT criticism. I'm having a blast. On the latest mission (the one with the Aviatik stuck in a descending orbit) I landed back at base at the same time as A Flight. The debriefing screen shows that I landed at Bertangles West and A flight landed at home. I've noticed on more than one occasion when I land at a divert aerodrome the debrief screen will show I've landed at home. Here's a shot from turning downwind. I took it because of the guy that landed off the aerodrome 1.4 NM to the north. And the debriefing screen.

So where did the Strutter carry bombs? I don't have a Sopwith reference book. The only way I was sure I had them was to cycle to the next weapon.

Much obliged. This is the two-seater, 70 Sqn RFC. Graphically the 40-pound bombs are missing. I had loaded up B Flight with them for an attack on a railway station.

Yesterday I noticed a squadron mate circling on the friendly side of NML. The activity label said he was Going Home. I rejoined on him and flew on his wing as he simply descended into the mud. The text color changed from green to black as expected. The debriefing screen showed that they both were okay, and there was no loss of an airplane, none being repaired. Today I watched an Aviatik (one in a pair) that was displaying Going Home go into a gradually descending orbit from 10,000 feet well inside Allied lines. My observer had just flamed the first Aviatik (I was flying below and in front of him), we turned to attack the trailer. Before I could perform a lead turn on him, he went into a left-hand orbit. He didn't fly a constant diameter circle. My observer managed to flame this one too. I don't recall seeing this before. Anybody else notice this behavior? Might it be a change to the DM?

I would really appreciate a functional logbook editor as well.

That is correct. Bertangles West is approx 4 NM away from where I landed.