FSX: The 1940 Fokker T.5 bomber released

Hi guys,

First of all, thanks for the enthusiasm, it's a real delight for me to see this!

One question: has anyone had problems with the radios? I've received messages from a user, who has problems with the radio. The symptoms are a bit strange, and I've never had problems, but maybe I overlooked something.

Greetings-

Downloaded her, installed her, took her for a quick spin(it does jump right off the runway, doesn't it?)... All I can say is WOW... what an achievement!
This work should be set up in an appropriate museum on a huge monitor where people can see a piece of history re-created in such beautiful detail.

Way to go, Daan! - Mike Z.

Mike, thanks! Yes, she's quite jumpy in take-off indeed. The run is in accordance to the original numbers, and the initial climb speed isn't that large. Anyway it keeps surprising me, too.

I do believe this can be fixed under the [propeller] section of the acft.cfg file by inserting "rotation = 1, 1" (or -1, -1 as the case may be). Leave the quotes out.

I'll see what I can fix. The main drawback is, that the starting animation is custom coded and completely passes the default starting.
 
Ditto, way to go!!

Same as all of the positive comments above. A real work of art, with great attention to detail, particularly impressed with the interior. It certainly gets airborne rapidly, and it initially took me some practice to nail the speed on final approach, but when it’s accomplished, beautiful three-pointers can be done. The only very minor problem I’ve had, is I can’t seem to un-cage the D.G. after setting runway heading. Any ideas? Again many congratulations. Magnificent.
 
Hi Cat,

Thanks for these words!

The D.G. is quite inoperational. Since its function wasn't clear to me, I neglected it.
Probably will need to enhance this as well.
 
Hi guys,

First of all, thanks for the enthusiasm, it's a real delight for me to see this!

One question: has anyone had problems with the radios? I've received messages from a user, who has problems with the radio. The symptoms are a bit strange, and I've never had problems, but maybe I overlooked something.



Mike, thanks! Yes, she's quite jumpy in take-off indeed. The run is in accordance to the original numbers, and the initial climb speed isn't that large. Anyway it keeps surprising me, too.


Hi Dutcheeseblend,

Yes I have issues with the radio's (and the autopilot, so probably the avionics are not started up correctly). Since I allways start from Cold & Dark I thought that I was doing something wrong in the start-up procedure.
This did not deter from having lots of fun with this machine! :sentimental:

Brgds,

Marijn
 
Hi Marijn,

That's a pity.
Can you describe the behaviour?
I'm not a solid coder, so :wiggle:

I might need a coder to look at it.

Cheers, Daan
 
Same old issue I guess. I started up from cold & dark by closing all systems on the T5.
Then follow the procedures as per the manual.

When I start up by using the default Cessna 172 > bring that to close & dark and then switch the airplane to the T5 all is well...:applause:

Radio's and autopilot work as expected.
 
Hi Daan,

I did some more checking, when starting up with the T5 as my plane of choice no radios or AP available. Even when just left as is (i.e no Cold & Dark set-up) No mather what I do to whatever switch is making the radios come alive.
However, as stated before, starting a default flight with a default plane and then switch to the T5 makes it all work right!

So if anybody is having the same issue (probably related to our specific set-up or system) just start a default flight with a default plane and then switch to the T5.

I am running FSX-SE on windows 10 and some planes need to be the start-up plane ( most A2A aircraft, MJ C-47 for example) and some others only work if the flight was started up using a default plane.

A bit of trail and error but... it works!

So I am flying around my virtual world in a wonderfull T5 and could not be more happy:jump:
 
Hi Daan,

I did some more checking, when starting up with the T5 as my plane of choice no radios or AP available. Even when just left as is (i.e no Cold & Dark set-up) No mather what I do to whatever switch is making the radios come alive.
However, as stated before, starting a default flight with a default plane and then switch to the T5 makes it all work right!

So if anybody is having the same issue (probably related to our specific set-up or system) just start a default flight with a default plane and then switch to the T5.

I am running FSX-SE on windows 10 and some planes need to be the start-up plane ( most A2A aircraft, MJ C-47 for example) and some others only work if the flight was started up using a default plane.

A bit of trail and error but... it works!

So I am flying around my virtual world in a wonderfull T5 and could not be more happy:jump:
I've been in touch with Daan over the same issue and have found the workaround as you indicated. In one instance the radio worked for a few minutes, then went dead. I'm running FSXA in Win 8.1.
 
reloading the aircraft after startup of your flight (selecting the same aircraft from your menu) whilst sitting in the VC also works...for me at least:jump:
 
reloading the aircraft after startup of your flight (selecting the same aircraft from your menu) whilst sitting in the VC also works...for me at least:jump:
Yeah, that works. However, after a couple if minutes the radio dies. The ATC window is open, but I cannot transmit nor receive any messages until I reload the aircraft. Almost as if there is a built-in power failure or fault.
 
On page 33 of the manual there is reference to the "veld" knob. (Knob 6 on the electrical panel.)Veld is field in English. This knob adjusts the field coils of the generators to keep the supply vs load in check. If you start putting too much load on the system without adjusting the generator output, power will start to draw from the batteries draining them. In short we are the voltage regulator in this plane!

Watch the three ammeters on the electrical panel. The upper one is the draw on the system. It is around 50A. You need to adjust the generator output via the Veld knob to get the upper ammeter to zero out. All electrical power is then being supplied by the generators (using both in parallel reduces the strain on each) while the battery maintains its charge. If you turn the battery switch off in the cockpit the amps on the upper meter will go from zero to the 25A on the left indicating a charge. (The meter actually pegs out as you are supplying the battery with whatever is coming out of the generator(s).) The voltmeter however does not go to zero so it must be directly attached to the battery at all times. If you fly around with the landing lights on and the gens off you will see the volts start to drop.

In addition from that awesome bit of programming in the sim this thing is just top shelf! I absolutely LOVE the view out the front when taxying! I would like to shake the hand of whoever at Fokker decided to mount the instrument panel off to the side like that! The only thing I myself am having difficulty with is elevator trim. I'll set it and it'll fly level for a while then climb. I'll re-trim, it'll fly level for a while then dive. Is this a glitch or is it true to life?
 
On page 33 of the manual there is reference to the "veld" knob. (Knob 6 on the electrical panel.)Veld is field in English. This knob adjusts the field coils of the generators to keep the supply vs load in check. If you start putting too much load on the system without adjusting the generator output, power will start to draw from the batteries draining them. In short we are the voltage regulator in this plane!

Watch the three ammeters on the electrical panel. The upper one is the draw on the system. It is around 50A. You need to adjust the generator output via the Veld knob to get the upper ammeter to zero out. All electrical power is then being supplied by the generators (using both in parallel reduces the strain on each) while the battery maintains its charge. If you turn the battery switch off in the cockpit the amps on the upper meter will go from zero to the 25A on the left indicating a charge. (The meter actually pegs out as you are supplying the battery with whatever is coming out of the generator(s).) The voltmeter however does not go to zero so it must be directly attached to the battery at all times. If you fly around with the landing lights on and the gens off you will see the volts start to drop.

In addition from that awesome bit of programming in the sim this thing is just top shelf! I absolutely LOVE the view out the front when taxying! I would like to shake the hand of whoever at Fokker decided to mount the instrument panel off to the side like that! The only thing I myself am having difficulty with is elevator trim. I'll set it and it'll fly level for a while then climb. I'll re-trim, it'll fly level for a while then dive. Is this a glitch or is it true to life?

Hi Josh!,

That electrical behaviour is exactly the way I intended it to work.
The D.21 also has this kind of system, but not sophisticated. We found out how it worked with the help of an ESA electrical engineer.
Glad to see that it is acknowledged!
The voltmeter is always connected to the battery. In fact, I created an xml gauge that has a battery state of charge, which is in fact just a number (indicating the Coulombs) and when this number reaches a certain value (-26xxxx), all systems should go black.
This system also ensures one can start the engine until the battery is drained. So you can wait for a number of blades passing by, etc. This only applies when using the manual starting procedure.

The cockpit layout design ultimately proved not very efficient, the military eventually advised to make a side-by-side cockpit next time. Yet, it is very useful at high attitude situations.

There are stories from this alley. You couldn't walk while connected to the oxygen supply units, so it happened often that someone went unconscious. "Dan lag er weer een blauw in het gangetje."

Regarding the trims: the way you describe it, it's always been like that. Now I must admit I'm not a real life aviator. The airplane is quite easy to fly, so if that's the only difficulty...

Why the radio's refuse to work in some cases, is quite unclear to me. It might be the electrical system, but this only prevents one to use the radios from the machine interface. From the ATC window it should still work. And besides that, the system won't drain in 'a few minutes'. Every xml gauge has its own update frequency, does the framerate matter for that?

Kind regards,

Daan
 
Hi Josh!,

That electrical behaviour is exactly the way I intended it to work.
The D.21 also has this kind of system, but not sophisticated. We found out how it worked with the help of an ESA electrical engineer.
Glad to see that it is acknowledged!
The voltmeter is always connected to the battery. In fact, I created an xml gauge that has a battery state of charge, which is in fact just a number (indicating the Coulombs) and when this number reaches a certain value (-26xxxx), all systems should go black.
This system also ensures one can start the engine until the battery is drained. So you can wait for a number of blades passing by, etc. This only applies when using the manual starting procedure.

The cockpit layout design ultimately proved not very efficient, the military eventually advised to make a side-by-side cockpit next time. Yet, it is very useful at high attitude situations.

There are stories from this alley. You couldn't walk while connected to the oxygen supply units, so it happened often that someone went unconscious. "Dan lag er weer een blauw in het gangetje."

Regarding the trims: the way you describe it, it's always been like that. Now I must admit I'm not a real life aviator. The airplane is quite easy to fly, so if that's the only difficulty...

Why the radio's refuse to work in some cases, is quite unclear to me. It might be the electrical system, but this only prevents one to use the radios from the machine interface. From the ATC window it should still work. And besides that, the system won't drain in 'a few minutes'. Every xml gauge has its own update frequency, does the framerate matter for that?

Kind regards,

Daan
Yes. I have not experienced the ATC window (radios) not working. What I observed while using the electrical system is that the battery drain with the generators off and equipment on is really quite slow and it takes a while to notice a voltage drop.
 
Yes. I have not experienced the ATC window (radios) not working. What I observed while using the electrical system is that the battery drain with the generators off and equipment on is really quite slow and it takes a while to notice a voltage drop.

Sure is quite slow. It can run on full load some twenty minutes I believe (tested it long ago). The battery has a capacity of 73 Ah.

Edit: though maybe that would heat the battery too much. Not simulated however.
 
Guys, a few thoughts from me.

Right now after release, there's a few issues surfacing:
- Incorrect prop rotation direction
- Inoperative Directional Gyro
- Manual references to Bombsight are incorrect
- Radio and autopilot problems (still not solved)
- Base material color appears dirty
- Crew texture sheet need optimization
- Users not installing the P3D panel folder to enjoy the enhanced sounds

What do you think would be most effective? Publishing a hotfix or waiting some time and then release a V1.2?

Let me know.
 
I would prefer waiting for 1.2. Incremental updates at random can become confusing and later on, re-installs can become problematic if you also have to keep track of the sequence of the update releases.
 
Hi Daan,

She is perfectly flyable and does not need an ad-hoc fix IMHO. If you want to address some issues, best would be to release a "complete" fix as a new version.
Just my two cents..:playful:

But there is one other issue.... maybe you should add a notice about the addictive nature of this plane. I can't leave her alone!:wavey:

brgds,

Marijn
 
My preference would be not to release anything until there is a fix for the radio and autopilot. I haven't noticed the other issues as I've been more focused on interacting with ground control and ATC. I'd be satisfied with a temporary fix that would circumvent the modeled radio aspect and rely on the stock FSX radios.
 
I would prefer waiting for 1.2. Incremental updates at random can become confusing and later on, re-installs can become problematic if you also have to keep track of the sequence of the update releases.

I fully agree, take your time to release V1.2 , no hurry :engel016:
 
Back
Top