Fokker D.21 conversion for MSFS2020

Alex, what a wonderful screenshots!

Keith, you mean the canopy and window clickspots? Unfortunately, I can't help you on this, since I don't have MSFS2020 myself. Probably in the future, but first get to finish that T.5 bomber. And then I may need a new rig.
 
Oooooh, I love this! OK, it's a port-over, so some things don't work (couldn't shut her down), but it feels great to go HuBoBe over the Netherlands with this..

jk8030

jk8020

jk8010

jk8014

jk8009

and maybe the shine is a bit too much, but I still love it!
 
Jankees - you can shut her down (and restart :) ) if you fold the LD door/canopy open - this unmasks all the engine controls for mousing.
Basically do all pre and post flight with the lid off.
Only concern is that if you run out of fuel mid flight you have to open the canopy to select the reserve fuel :(

Dutcheeseblend - no worries, though maybe you can throw light on the clickspot masking - on imports there are always one or two clickspots that cover the whole screen and sometimes mask the spots beneath. In this case its the Window sliders and door/canopy open - are they the first/last defined? Are they in some way different to all the others?

Thanks
Keith
 
Jankees - you can shut her down (and restart :) ) if you fold the LD door/canopy open - this unmasks all the engine controls for mousing.
Basically do all pre and post flight with the lid off.
Only concern is that if you run out of fuel mid flight you have to open the canopy to select the reserve fuel :(

Dutcheeseblend - no worries, though maybe you can throw light on the clickspot masking - on imports there are always one or two clickspots that cover the whole screen and sometimes mask the spots beneath. In this case its the Window sliders and door/canopy open - are they the first/last defined? Are they in some way different to all the others?

Thanks
Keith

Hi Keith,

Well, this clickspot masking thingy is quite a new phenomenon for me. Haven't ever heard about that before.
Do these clickspots work with the bounding box of the object rather than the "physical" model?

Regards, Daan
 
Thank you, it is great to have this excellent aircraft in MSFS!

One of these days I need to start researching my grandmother's Dutch ancestry (Vander Syde).











 
Nice pics!
Vander Syde sounds more Belgian to me, in the Netherlands it would be van der Syde. Syde is an old spelling of the present day Zijde, or silk. Maybe they were weavers originally?
 
Thank you Jankees! Traditionally, at least as far as I know, it has typically been written as just one name here in the US and in the UK ("VanderSyde"), but sometimes split in two, but yeah it would make sense to me that it would have been split in three at one time. It was always understood within my grandmother's family that they were of Dutch ancestry - according to my grandmother, who has since past, her dad only wanted her to marry a fellow from another Dutch family (but which didn't happen). It is interesting to learn about the modern word for "Syde" being "Zijde"/silk.
 
Nice shots guys, I recognise Bakkum, Haarlem and Uitgeest, but why doesn't anyone ever fly over Noordwijk or Voorhout?

I did a small query at the "Familienamen bank" (Dutch family name register) on the name "van der Zeijden" as "van der Syde" didn't exist. As you see the name is not really connected to one particular part of the Netherlands. In 2007 there were 7 persons registered with the family name van der Zijde. Which seems to be a name related to Amsterdam from which some have move to the polders (after 1965). As you can see in 2007 there were 218 persons with the name "van der Zeijden" name written in 2 different ways.

As the French under Napoleon started our name register, Dutch names where often registered by French civil servants. My family name was "Vinck" until the French shortened it to "Vink". Also many Dutch names were Anglicised when Dutch families migrated to the US, Australia and Canada. "Vanderbilt", was originally "van der Bilt", Vanderberg's real name is Adje van den Berg etc.. This was also common for town names. Brooklyn was originally Breukelen, Harlem was Haarlem.

dR2DRrX.jpg


KV8sxMX.jpg


Cheers,
Huub
 
That is fantastic, Huub! I really appreciate that very much. This will certainly motivate me to try and solve the puzzle of tracing the family line back to the Netherlands. I know just about every generation of my Terrell (Tyrrell/Tirrell/Tirel) family line since it began just over 1,000 years ago, and earlier generations over the course of centuries before that, but my other family trees only go back to about the mid-late 1800's as far as the generations I have information on. A big problem, as you've alluded to, is the changes in spellings.

Sorry guys for taking this thread off track, but many thanks again, Jankees and Huub!

Thank you again, Daan, for this fantastic aircraft! I've been really looking forward to seeing the reproduction based at Hoogeveen, finished in this same paint scheme, flying soon.

 
Thank you again, Daan, for this fantastic aircraft! I've been really looking forward to seeing the reproduction based at Hoogeveen, finished in this same paint scheme, flying soon.

More than welcome John! I absolutely love to see all screenshots. Great enjoyment for me! It's now nearly six years ago when it was initially released (november 2014). And, that also means it's over six years that I started with the T.5 (september 2014). That said, I expect to get a pre-final beta done next week.

I've been several times to Hoogeveen. The project is really fantastic. When you stand next to it, the aircraft is really big, sturdy and spacious. Immediate cause is, of course, the big engine (over 1.30 m in diameter), which makes for a spacious cockpit. I made this photograph there:
Aum_bJCxMxi5W2BG5atqaHLu1iebaXSNbnzPm7c6ePvDREBE7rnpAaCUfbSSAuMK_gYzgPn_gR8YrNWMOaPCkJ0JgyDmzh_RUpHIPSqb5vNC2wkUBP02_wzIomq-9sWWe-CkgWgH18ExMNW3jzuG4cs5e-m2sWIsZFnd63ZXlcBsDJzagubqSA4xX-H212K9aXrh6vm8BK464tvPj3h2Eq-A7zJqTWLfgGY6k8xiCO5ehAFU1GUUZMAIyN8XgfDSB7q298rDtk24m2L3AzNzhiJISvWVEWh0Ujr-_Y5Dadjwg9gSJQWGPKaeXt-WpOGpRle12-1bxaEk6U6FVeZV1J8mfwTk2v0MdgTcSwp9eizQ3xnuF-naPTolrcRLF5bD1xRAFI6OE3m4o65i1416jK8aH5K7lrnX_R-iVkvLx1PbrzqGhf24sT9bZA7MFGZfBDw3iL8B-sAv54ER32T6u-VANzE23_Nb2nqwu7yNZy5lxeIFcCwkuqqPedVzl-30-HoaQIzVV7svchu9v0lGaHL7t-YdDIcXBcoSIx5PVydGbO1cA1OKwHtjwdE76bRbzz5YYFIoEyxVtptS6jNM3_3sY4LHZufrxSWnt0U5wH6ZskaBVMrEpl069irLSfLt4f2hWjHmmlRv2ToMQhpdFQfLlxV6k-qep-dt1rDZW1eW5UaqXHNE6MY9a5zs=w1294-h970-no


rU_RQz43CuR1005lFUXuZVUKJPnNHgJ4IlzaQqnTmcfey-IOOwsxPEfYcAKvV0ARs5vqYWGzgeulwGF7hyg766c4pWQwCKwPtTHc3ayAjZ_AzpjuSDAtImcpZOv949GEfqBY7eSJQaBoG3_lSAYohnfEhk6DsJGuIzx3c42iqCg0ZgzN1wtEv_Ont0oKaKXZ_Qw6CupTQ3kVdHboZp6iVc9DX0udawp2mxC-zfNWraHm8ClWeSxADuXJ6q46JVJOhI4WHJ3knj14RJkS7NLV7JIYkKawMkLf3_SQ-hqgt_Kok1IILIc-9JKqbmAXQ5sDZ2Ncl9oxHaQlNFuNLP5l2CW0a-XR6RcHEWy5XiOP8bUVkrfdgMJllAeWJOqkyGBeVktuTnBTxfzYQZOTmuuL4VGnDu9h2KVvV4J-i1y9OpaCWNhaikcfq4igr4VD-FYpRiXreyGl1ibACqa7lOMfmJ75SAfg8LBqVw_G_Q-SJLYpmBwVg-QKMyNlfobf7OG-ZHEDJeMTJgKOxqlkA22nxOQen2Kkarrb9HLOSdN3sdTLSI3F7ijxbefrp_J5trL_MGq-9pNfUHa309ODEhll33IMrXODs9122j-wZ1tBwDznTkESGH9s6Xq_3iBNRyCJzuzCkk_Pu6VdC60u4pjSms5qdCAlQf0SyNL044V7Hs0kGuAirdBGrPP2pbo9=w1294-h970-no


KkGq39t3gL5BoXU9pdgdrnrTIBfSgMnx7797-MwwXOisglVjhlxHdJnF-BTdcSrnYcwXFh-R35p7Bfv61um5heTrvKWTWRFrknN3bbDs1vQ9l2aIRzcYpCNsiIfuK8U7hyZ5IVklS5hrcvorQriAMthSjcNasyQbGha1zTrQTSdjMvhpubi7QKJKtztLYh3tCbHWInWSw53UGPlgllYeLd7Gg2RIHs6xm0qJvK9J8Nx197VE46GPc9mvwxbwsr4aRhr2fIlBlm_AdEOUv6cMw0RfjYiiT9npWUW4Gxj9AJ2gWFDvjznZwxGQ76Dk9gMXzmKKaVV-_J3qs1hCRIf74ucA4Yt2ZTTEg3yig18yPddkyk_-WFIHZJTBkLxR0pdoj03wRvXpIPXvJSfYah2YkDiNR4DsWbrPV9Fyuo9ZJp6k__RSgrSQ35gjcjksG83Dr5t_n_7zt9bMce2_xC2HJ-3p8UN1I5NQ46ohmNa2Kp0urlORb-UmJBJhlAByYU6O1WMPgBsBditVL577pSRsN-f2LcNEMCi7ZNSsXMO46axroXtEj_AUFmLand1YbppmYhklVCMVtRmeSL_f2z9iDxVZGw9Wgd4ESJuJ1S35fCeGcBxljvCa-vI1GcYR_UPBZsitPZUU8vDq6ja_2ZHMZHGfKJVR7C7xyF4BZ0tsYF2oY5jxMOWvO8iMRQWb=w1294-h970-no
 
I've posted a video illustrating the click-spot problem in the hope we can get to the bottom of it..

All the clickable locations are over-ridden by either the window open or cockpit open click-spots.
At 2:12+ the cockpit is opened and drops away, taking it's click-spot with it and making all the click-spots on the LH side suddenly work as intended :)
Opening the windows has no effect as the click-spot doesn't move.

Cheers
Keith
 
I've posted a video illustrating the click-spot problem in the hope we can get to the bottom of it..

All the clickable locations are over-ridden by either the window open or cockpit open click-spots.
At 2:12+ the cockpit is opened and drops away, taking it's click-spot with it and making all the click-spots on the LH side suddenly work as intended :)
Opening the windows has no effect as the click-spot doesn't move.

Cheers
Keith
Hi,

I am currently carrying my Cessna 150s to MSFS and I have the same problem. I've been trying to get around these problems for more than 3 weeks without success.
It seems to me that the problem of the management of the mouse rectangles is a problem of MDL management by ASOBO. In their version 1.8.3.0 they tried to circumvent this problem awkwardly by removing completely the management of this function in the MDLs and they put it back following the uploads in the Zendesk .
In the current version, some mouse rectangles behave strangely, they seem to hide the whole screen surface. This phenomenon is random and seems to depend on the hierarchy of objects in the modeling tool (Gmax, Blender or 3DS). By attaching these mouse rectangles to other parts, using dummies or changing the relationship between objects, this defect can sometimes be eliminated.

Some of my aircraft have this problem and others are absolutely not subject to it. That's why I think the problem is on the ASOBO side and not in our files. Moreover these planes behave quite normally in FSX or Prepar3D v1.x - v5.

Didier "Lagaffe"
 
Back
Top