• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MV-22B Osprey

pinkjr said:
will try sir. I think I tried using "/" already.
Right. Deff not the first time. Can you please slap me stupid! :)
Problem solved....working perfectly.

Thanks guys!
Click to expand...
Glad you found it.
Good thing I have a lot of experiance in what users can do wrong with editting config files ......
Mostly because I made those mistakes myself too ...LoL

Cheers, Rob
 
- moving over model and model code done.
it slightly same, but have major different inside it ( code, model and texture).

2017-9-25_23-7-14-319.jpg



2017-10-5_9-25-38-125.jpg



2017-10-5_9-31-46-328.jpg




2017-10-5_9-37-18-924.jpg




2017-10-5_9-35-37-571.jpg
 
It easy, just thinking, what variable to command ramp to that position. It should in auto mode.
 
once I give a touch in Osprey many update coming, this another update in last 2 days.
Thanks to Bill Leaming for his awesome xml gauge. at first thought that difficult gauge, and I wrong, it quite simple (of course need some basic experience in modeling and xml). Dimming light gauge, so panel light can be adjustable. next port is text electro-illuminate

Day with fully "brightness"
2017-11-26_12-32-39-78.jpg



Night with fully "brightness"
2017-11-26_12-33-4-249.jpg
 
kalong said:
once I give a touch in Osprey many update coming, this another update in last 2 days.
Thanks to Bill Leaming for his awesome xml gauge. at first thought that difficult gauge, and I wrong, it quite simple (of course need some basic experience in modeling and xml). Dimming light gauge, so panel light can be adjustable. next port is text electro-illuminate

Day with fully "brightness"
View attachment 38118


Night with fully "brightness"
View attachment 38119
Click to expand...

Wow, that looks amazing! I am very interested to know how one does that, if you and Bill would be willing to share this magic. :rolleyes:
EDIT: found the discussion thread, very cool stuff!
 
Last edited:
It easy, just thinking, what variable to command ramp to that position. It should in auto mode.
Click to expand...
I dont know how you executed the system you just made, but in my head I was thinking of something like this (refering to the 3 door ramp switches):
If Left switch down, then ramp is LEVEL
If Left and Middle switch down, then ramp is FULL OPEN
If Middle switch down, then Top-half of Ramp is OPEN
If Middle and Right switch down, then Top-half of ramp and Top-half of Side Door is OPEN
If Right switch down, then Side Door FULL OPEN
If all 3 switches down, then all doors FULL OPEN.


For all I know what I suggested above might go against your whole coding for your new system or might not be relative to what you were talking about. But I just wanted to let you know what I thought of that might work.
 
Unfortunately my new system doesn't use button combination. I'm consider with pilot workload and learning curve.
Left switch = ramp open/close
Middle = auto/manual
Right = side door open/close

When middle switch at manual (default), pilot can use keyboard to open door. SHIFT + E. and it only made door all the way down, and never made door up/half position.
When middle switch at auto, default keyboard command will disable. Open and close door only from the switch. When a/c stay still on ground door will fully open, but when aircraft in the air or speed above 3 knots, door will auto half close.
I just thinking, if altitude above 1000ft from ground or speed above 200 knots, lower ramp door will close.

This door simulation not real aircraft did, cause real aircraft use real human to deal with door/ramp usage
 
change lighting system from overhead to CDU screen. it made closer to reality. uh.... still lot of work, need update the Flight Manual.


old PRIMARY LIGHTING is for beacon, strobe and nav, now it became VC lighting system ( see picture on previous post) CPLT, OVHD and PLT.

2017-11-30_11-9-22-906.jpg




this external lighting system screen, as @Heater ever request, now lighting system can be set manually by pilot. Bright/Dim and IR lighting aren't simulated, due to variable multiplayer limitation and Sim Engine limitation.
to open menu lighting system on CDU use LTS button on VC keyboard

2017-11-30_11-8-44-835.jpg
 
I am officially losing my mind now. This is Fantastic Maryadi, thanks for integrating that!!! The amount of detail you put in is phenominal!!
 
there still lot more of detail, which may made never ending of waiting ... so I'll stop upgrade at this point for release 2.0 and leave remain detail for next update/release.
 
You must log in or register to reply here.
Back
Top