-
There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.
The Staff of SOH
Ito's Fairy Rotodyne
- Thread starter OBIO
- Start date
For those not familiar with Ito's Rotodyne, or for those who have not really put the polish to it:
I installed Rob Barendregt's xlm based Rotodyne VTOL/Hover gauge set up...and what a difference it made in Ito's Rotodyne. That big egg beater sure is fun to fly now. Lifts off the ground as smooth as you please, hovers like a nosey busy-body just waiting to catch the latest gossip (which means it hovers very very well). The suggested change in the turbine static thrust (something like that) really took the heat out of the Roto and has it flying sweetly without all the dreaded OVERSPEED warnings.
And, a bit of a found treasure. Digging around in the Alpha Oldies stuff, I came across their older freeware Rotodyne..downloaded it and found that it comes with a rather decent panel that works quite well for Ito's Rotodyne. Only two of the guages in the stock panel set up did not show up in FS2004...the attitude gauge and the landing gear gauge...short work to swap them for a couple of FS2004 gauges.
I have added a slew of VC lights to Ito's Rotodyne, and the bird looks very nice flying at night.
OBIO
I installed Rob Barendregt's xlm based Rotodyne VTOL/Hover gauge set up...and what a difference it made in Ito's Rotodyne. That big egg beater sure is fun to fly now. Lifts off the ground as smooth as you please, hovers like a nosey busy-body just waiting to catch the latest gossip (which means it hovers very very well). The suggested change in the turbine static thrust (something like that) really took the heat out of the Roto and has it flying sweetly without all the dreaded OVERSPEED warnings.
And, a bit of a found treasure. Digging around in the Alpha Oldies stuff, I came across their older freeware Rotodyne..downloaded it and found that it comes with a rather decent panel that works quite well for Ito's Rotodyne. Only two of the guages in the stock panel set up did not show up in FS2004...the attitude gauge and the landing gear gauge...short work to swap them for a couple of FS2004 gauges.
I have added a slew of VC lights to Ito's Rotodyne, and the bird looks very nice flying at night.
OBIO
If you add a gauge that automatically controls the flaps and thereby the RCB VSTOL gauge it gets even easire to fly than the lovely docile beast that it is....
If anyone wants to do this then make a copy of one of the .xml files in the rcb-gauges folder.
Open this copied file in notepad.
Delete its contents.
Copy the following in in its place.
<Gauge Name="Autoflap">
<Comment>
Toggles flap based on airspeed, currently 35kts. To be used for Freeware only.</Comment>
<Element>
<Select>
<Value>
(A:AIRSPEED INDICATED,knots) 35 < if{ (>K:FLAPS_DOWN) } els{ (>K:FLAPS_UP) }
</Value>
</Select>
</Element>
</Gauge>
Save the file
Rename it as : VSTOL_flap_control
In the rotodyne panel cfg add the line : gauge##=rcb-gauges!VSTOL_flap_control, 1,1,1,1
Also in the cfg file add the following under the VC cockpit section : gauge##=rcb-gauges!VSTOL_flap_control, 0,0
Save the file.
Your flaps should now work automatically.
Hope this is of use to some people.
M
If anyone wants to do this then make a copy of one of the .xml files in the rcb-gauges folder.
Open this copied file in notepad.
Delete its contents.
Copy the following in in its place.
<Gauge Name="Autoflap">
<Comment>
Toggles flap based on airspeed, currently 35kts. To be used for Freeware only.</Comment>
<Element>
<Select>
<Value>
(A:AIRSPEED INDICATED,knots) 35 < if{ (>K:FLAPS_DOWN) } els{ (>K:FLAPS_UP) }
</Value>
</Select>
</Element>
</Gauge>
Save the file
Rename it as : VSTOL_flap_control
In the rotodyne panel cfg add the line : gauge##=rcb-gauges!VSTOL_flap_control, 1,1,1,1
Also in the cfg file add the following under the VC cockpit section : gauge##=rcb-gauges!VSTOL_flap_control, 0,0
Save the file.
Your flaps should now work automatically.
Hope this is of use to some people.
M
Firebar
I gave your Auto Flaps gauge a try.....it works great for take offs, but makes landing in VTOL mode a real PITA. In order to get air speed below 35 knots to get back into VTOL mode, I had to chop power to nothing, put the Rotodyne into a very nose high attitude, then scramble like heck to get the craft out of a fatal stall using nothing but the rotor before slamming into the ground. I could not manually deploy the flaps to get into VTOL mode.
I have no clue about gauge programming what so ever...so please know that I am in total awe of what you have produced with the Auto Flap Gauge. Is there a way to over come this issue?
OBIO
I gave your Auto Flaps gauge a try.....it works great for take offs, but makes landing in VTOL mode a real PITA. In order to get air speed below 35 knots to get back into VTOL mode, I had to chop power to nothing, put the Rotodyne into a very nose high attitude, then scramble like heck to get the craft out of a fatal stall using nothing but the rotor before slamming into the ground. I could not manually deploy the flaps to get into VTOL mode.
I have no clue about gauge programming what so ever...so please know that I am in total awe of what you have produced with the Auto Flap Gauge. Is there a way to over come this issue?
OBIO
Right here's what I've come up with (not much testing - I have homework to do)
!!!!!CREATE COPIES OF ALL FILES TO MODIFY FIRST!!!!!
Create Another XML file in the rcb-gauges file like previously.
Rename it : VSTOL_Auto_Spoilers
Delete its contents.
Paste in the following (its a bit untidy I know, but it seems to work (fingers crossed)) :
<Gauge Name="Autospoiler">
<Comment>
Toggles spoilers based on fuelflow. For Freeware Only.
</Comment>
<Element>
<Select>
<Value>
(A:ENG1 FUEL FLOW GPH,gallons per hour) 35 < if{ (A:ENG2 FUEL FLOW GPH,gallons per hour) 35 < if{ (>K:SPOILERS_ON) } els{ (>K:SPOILERS_OFF) } } els{ (A:ENG2 FUEL FLOW GPH,gallons per hour) 35 < if{ (>K:SPOILERS_OFF) } els{ (>K:SPOILERS_OFF) } }
</Value>
</Select>
</Element>
</Gauge>
Save the File.
In the rotodyne panel cfg add the line : gauge##=rcb-gauges!VSTOL_Auto_Spoilers, 1,1,1,1
Also in the cfg file add the following under the VC cockpit section : gauge##=rcb-gauges!VSTOL_Auto Spoilers, 0,0
This Gauge should trigger spoilers when the fuel flow on both engines is less than 35 gph, I was origonally going to use an average but I couldn't get it to work.
To the aircraft CFG file add the lines :
spoiler_extension_time=0.005
spoiler_limit=50.0
The latter should be pasted over the origonal data for that value. Both go in the [airplane_geometry] section.
This assumes you have air ed installed.
Open the AIR file and find the section intitled Flight Dynamics.
Change Fuselage Drag to about 90-100
Change Spoiler Drag to about 200-250
Change Flaps Drag to 200
Save The File
I have also changed the speed value in the first gauge to 45
Hopefully this should work
M
!!!!!CREATE COPIES OF ALL FILES TO MODIFY FIRST!!!!!
Create Another XML file in the rcb-gauges file like previously.
Rename it : VSTOL_Auto_Spoilers
Delete its contents.
Paste in the following (its a bit untidy I know, but it seems to work (fingers crossed)) :
<Gauge Name="Autospoiler">
<Comment>
Toggles spoilers based on fuelflow. For Freeware Only.
</Comment>
<Element>
<Select>
<Value>
(A:ENG1 FUEL FLOW GPH,gallons per hour) 35 < if{ (A:ENG2 FUEL FLOW GPH,gallons per hour) 35 < if{ (>K:SPOILERS_ON) } els{ (>K:SPOILERS_OFF) } } els{ (A:ENG2 FUEL FLOW GPH,gallons per hour) 35 < if{ (>K:SPOILERS_OFF) } els{ (>K:SPOILERS_OFF) } }
</Value>
</Select>
</Element>
</Gauge>
Save the File.
In the rotodyne panel cfg add the line : gauge##=rcb-gauges!VSTOL_Auto_Spoilers, 1,1,1,1
Also in the cfg file add the following under the VC cockpit section : gauge##=rcb-gauges!VSTOL_Auto Spoilers, 0,0
This Gauge should trigger spoilers when the fuel flow on both engines is less than 35 gph, I was origonally going to use an average but I couldn't get it to work.
To the aircraft CFG file add the lines :
spoiler_extension_time=0.005
spoiler_limit=50.0
The latter should be pasted over the origonal data for that value. Both go in the [airplane_geometry] section.
This assumes you have air ed installed.
Open the AIR file and find the section intitled Flight Dynamics.
Change Fuselage Drag to about 90-100
Change Spoiler Drag to about 200-250
Change Flaps Drag to 200
Save The File
I have also changed the speed value in the first gauge to 45
Hopefully this should work
M
Hi,
Allthough I think adding a "foolproof" Auto-VTOL switching criterium (one which has no side-effects, like: still have the possibility to do normal STOL takeoffs/landings) is a lot more complex,I must warn you about the way you suggest to code such functions.
(That is: in case you are unaware of this).
Your way of coding these flaps and spoiler handling induces the infamous "continuous event" bug, where multi-keystroke functions like pushback, select engine, select exit, etc etc will fail sometimes because these gauges continuously fire spoiler/flaps handling events.
A better way of coding is to first test if the flaps/spoiler handle is in the wrong position, and only then issue the appropriate event.
Regards, Rob
I bow to the master at this sort of stuff.
I wasn't aware of the multi keystroke failure thingy, its an interesting point. Why does it induce a continous bug event (although engine select has never worked for me...) in something that seems completely unrelated? All that I have been trying to do is to get the VTOl to kick in automatically, as habving to switch it on is a little unreal (and a pain if you forget).
I have to say I do love your gauges, especially the look of the A2A fuelling gauge that had some screenshots posted some time ago.
Cheers
M
I wasn't aware of the multi keystroke failure thingy, its an interesting point. Why does it induce a continous bug event (although engine select has never worked for me...) in something that seems completely unrelated? All that I have been trying to do is to get the VTOl to kick in automatically, as habving to switch it on is a little unreal (and a pain if you forget).
I have to say I do love your gauges, especially the look of the A2A fuelling gauge that had some screenshots posted some time ago.
Cheers
M
I'll try to explain.
Example: look at the default 737-400, and use a common (eng1/2) thottle axis on a joystick (or F1-F4 keys). And in the VC, observe the throttles.
Normally, your throttle commands both Eng1 and 2 throttles.
Now, type "E" (Select Engine) followed by "2" (on the main keyboard section, NOT Numpad).
Move the throttle, and noticed that only the throttle of Engine 2 moves.
This works as follows in FS:
When you type "E", FS is now in EngineSelect command mode.
Which means it now expects a "1" (Select-1 command) or "2" (Select-2) command (or both) to select an engine, for any action on an engine.
However, if FS sees any other event after the "E" command, it exits the EngineSelect mode , so if you type a "2" now it has lost the relation with the "E" command (the "2" event is ignored) , and now assumes you wanted to select Engine-1 (which is implicite).
Now, your gauge is scheduled by FS every 55 msec; with means that every 55 msec a flapsup or flapsdown event is generated.
IOW: to have the sequence "E" "2" work, you must type the "2" within 55 msec of the "E".. Try that
Note that even a commands like ChangeView is seen as an event.
And there are many of such Multi-Keystroke command (using a keystroke to select a "mode"), with FS waiting for generic inputs like "a number" or "+" (IncreaseSelection) ...
Clear ?
:ernae: Rob
Like I salute model builders and texture artists; area's in FS of which I don't have the first clue ....:help:
I'm only trying to say, that every one has his own expertise in MSFS addon design, and with the combined effort of all that knowledge we still have years to go in perfecting/improving/extending MSFS with addons.
Even with the current limitations of MSFS, and even without new versions of MSFS itself ...
:ernae: Rob
Now, your gauge is scheduled by FS every 55 msec; with means that every 55 msec a flapsup or flapsdown event is generated.
IOW: to have the sequence "E" "2" work, you must type the "2" within 55 msec of the "E".. Try that
sort of.....
so having the gauge effectively do the same as a keystroke interrupts certain commands...
would having a gauge affect an axis do the same thing? I seem to recall something about there being axis for many commands...
or would changing the refresh rate be enough to allow the time for selections to be made?
Very Informative.
Cheers
M
OkkeeYYYY
I was dabbing in that dark science myself (rotodyne) not so long ago and I do agree with Obio about the *&*)*&* panel (wife said the air around me was getting blue...) :isadizzy: otherwise is a hoot to fly specially with Rob Barendregt's gauge. I have to admit that I dit try it without and the results were both painful and untidy (parts all around the place, you know the drill...).
And sooo, Question, what is that alpha oldies stuff and where can I get it (panel), I would like to fly the thing without having to put my head through the window to see something :costumes:
Saludos
P.S. Repainting the little darling sounds like a good idea to me, lots of rivets, though :faint:
I was dabbing in that dark science myself (rotodyne) not so long ago and I do agree with Obio about the *&*)*&* panel (wife said the air around me was getting blue...) :isadizzy: otherwise is a hoot to fly specially with Rob Barendregt's gauge. I have to admit that I dit try it without and the results were both painful and untidy (parts all around the place, you know the drill...).
And sooo, Question, what is that alpha oldies stuff and where can I get it (panel), I would like to fly the thing without having to put my head through the window to see something :costumes:
Saludos
P.S. Repainting the little darling sounds like a good idea to me, lots of rivets, though :faint:
Here's a direct link to download the Alpha Sim Rotodyne for FS2002.
http://www.sim-outhouse.com/index.php?lloc=downloads&loc=downloads&page=downloads&FileUploadName=AlphaOldies&ammm=15&pap=8#download
The panel works great...just need to swap out the attitude and landing gear gauges as the ones specified in the panel.cfg are not included in FS2004. The view is much much better. One thing I did was to go into the aircraft.cfg and find the [Views] section and change the Eyepoint to make the VC view match the panel view. The panel is set up to fly the bird from the right hand seat while the VC view is set from the left hand seat. The stock VC eyepoint is -1.something and I just took out the - making it 1.something. That moves the VC view from left seat to right seat, thus matching the panel view.
OBIO
http://www.sim-outhouse.com/index.php?lloc=downloads&loc=downloads&page=downloads&FileUploadName=AlphaOldies&ammm=15&pap=8#download
The panel works great...just need to swap out the attitude and landing gear gauges as the ones specified in the panel.cfg are not included in FS2004. The view is much much better. One thing I did was to go into the aircraft.cfg and find the [Views] section and change the Eyepoint to make the VC view match the panel view. The panel is set up to fly the bird from the right hand seat while the VC view is set from the left hand seat. The stock VC eyepoint is -1.something and I just took out the - making it 1.something. That moves the VC view from left seat to right seat, thus matching the panel view.
OBIO