euroastar350
SOH-CM-2023
I'll check it out and update as necessary
-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
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 politician 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 among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
DeHavilland Dash 7 (FSX Native) released
- Thread starter euroastar350
- Start date
I do not know but Flightsim or Simviation libraries would be better places to check.
Paint Kit is here: http://www.sim-outhouse.com/sohforums/local_links.php?action=jump&catid=7&id=17833
BendyFlyer
Charter Member
Appreciate some feedback re VC
I love this aeroplane and this is a wonderful simulation. It performs exactly on the numbers and the VC is great. I would like to add a modest vote of thanks to you and others for this great piece of work. As a former real world Dash 8 driver I am seriously hooked on this aeroplane having spent many thousands of hourse in other STOL aircraft in and around Australia. I have transitioned across to the FSX Native model but I have encountered a couple of curious glitches and I would like some input from those familiar with 2D popups and VC's and FSX.
First I run an Intel 4GB dual core processor with a 2GB HP video card, this is tweaked a little but gives me relatively stable performance and generally no problems other than when the CPU is run hard with complicated terrain and weather graphics. I have FSX as a separate directory on my C drive and all my scenery is kept outside of FSX in special folders which is accessible via the FSX scenery library tools and works just fine.
Here are the problems, When I follow the cold n dark start procedure I could get it to start with the condition and prop levers in the recommended positions, the engines motored but did not catch. I then checked the alternative popups for the main and throttle quadrant, this showed that allthough I had selected the levers via the VC, they were still in the wrong position on the popup, when I corrected via the popup this they started properly. I have noted that using the VC controls the starter engage button light does not go out either when engines are running and the engine selector is in the OFF position and the starter control switch is placed in the normal position. The advice about cycling the props/power does get rid of some erroneous annunciator panel indicators. I have found that the VC power and prop levers work fine if I use CTL+E for auto engine start and in all other aspects work as I would expect and should. I have reloaded the files and tried again, once it did start as described, but then again it would not on later flights. I also find that the flap setting indicator seems to be out of whack when full flap (45) is selected. I am not sure but it also seems the on/off sense for overhead switches seems to be reversed on GENS, ICING and DC controls so that they do not match the overhead labels. I might add that the 2D popups work correctly but there is a mismatch here and there with some switches not working and others. I also found that if I attempted to the manual start and this did not work and reverted to the auto start key commands that it left the No2 engine in a high power situation which would not correct. At least the shutdown and feathering worked and I had a taste of some assymetic flying in this great machine, so a lesson learnt.
I had removed the automation dll from FSX some time ago as it caused me numerous problems with view switches in other models and wonder if this needs to be put back or updated on my system. Other than that I am at a loss to resolve these issues not that it would stop me from flying this bird to which I am now seriously addicted.
Here is a snap of the Dash with one feathered returning for a landing. I got the shockwave lights data from the OZX forum.
I love this aeroplane and this is a wonderful simulation. It performs exactly on the numbers and the VC is great. I would like to add a modest vote of thanks to you and others for this great piece of work. As a former real world Dash 8 driver I am seriously hooked on this aeroplane having spent many thousands of hourse in other STOL aircraft in and around Australia. I have transitioned across to the FSX Native model but I have encountered a couple of curious glitches and I would like some input from those familiar with 2D popups and VC's and FSX.
First I run an Intel 4GB dual core processor with a 2GB HP video card, this is tweaked a little but gives me relatively stable performance and generally no problems other than when the CPU is run hard with complicated terrain and weather graphics. I have FSX as a separate directory on my C drive and all my scenery is kept outside of FSX in special folders which is accessible via the FSX scenery library tools and works just fine.
Here are the problems, When I follow the cold n dark start procedure I could get it to start with the condition and prop levers in the recommended positions, the engines motored but did not catch. I then checked the alternative popups for the main and throttle quadrant, this showed that allthough I had selected the levers via the VC, they were still in the wrong position on the popup, when I corrected via the popup this they started properly. I have noted that using the VC controls the starter engage button light does not go out either when engines are running and the engine selector is in the OFF position and the starter control switch is placed in the normal position. The advice about cycling the props/power does get rid of some erroneous annunciator panel indicators. I have found that the VC power and prop levers work fine if I use CTL+E for auto engine start and in all other aspects work as I would expect and should. I have reloaded the files and tried again, once it did start as described, but then again it would not on later flights. I also find that the flap setting indicator seems to be out of whack when full flap (45) is selected. I am not sure but it also seems the on/off sense for overhead switches seems to be reversed on GENS, ICING and DC controls so that they do not match the overhead labels. I might add that the 2D popups work correctly but there is a mismatch here and there with some switches not working and others. I also found that if I attempted to the manual start and this did not work and reverted to the auto start key commands that it left the No2 engine in a high power situation which would not correct. At least the shutdown and feathering worked and I had a taste of some assymetic flying in this great machine, so a lesson learnt.
I had removed the automation dll from FSX some time ago as it caused me numerous problems with view switches in other models and wonder if this needs to be put back or updated on my system. Other than that I am at a loss to resolve these issues not that it would stop me from flying this bird to which I am now seriously addicted.
Here is a snap of the Dash with one feathered returning for a landing. I got the shockwave lights data from the OZX forum.
Bendyflyer,
Thanks for the comments.
The Dash 7 panel has about 500 callouts for gauges. This can create conflicts between the 2D and VC panels.
If you do not use the 2D panels, then I would recommend eliminating them as a test to see if most of the issues are resolved.
Make a copy of the panel.cfg before modifying.
Eliminate all 2D panels from the window00 thru window10.
[Window Titles]
Window00=Instrument panel
Window01=Engzoom
Window02=Pedestal
Window03=Navzoom
Window04=OVERHEAD_PANEL
Window05=GPS
Window06=AP Zoom
Window07=ECU Small
Window08=radio_stack_panel
Window09=TOL Cards
Window10=RwyInfo
Eliminate each of the associated [windowsnn] sections and gauges listed.
Leave only the vcockpitnn sections.
Test for results.
Unfortunately I no longer have a gauge programmer and my skills are limited to panel creation basics with some mods capabilities.
I hope this helps.
EDIT: Attached is a modified panel.cfg zipped for testing.
Thanks for the comments.
The Dash 7 panel has about 500 callouts for gauges. This can create conflicts between the 2D and VC panels.
If you do not use the 2D panels, then I would recommend eliminating them as a test to see if most of the issues are resolved.
Make a copy of the panel.cfg before modifying.
Eliminate all 2D panels from the window00 thru window10.
[Window Titles]
Window00=Instrument panel
Window01=Engzoom
Window02=Pedestal
Window03=Navzoom
Window04=OVERHEAD_PANEL
Window05=GPS
Window06=AP Zoom
Window07=ECU Small
Window08=radio_stack_panel
Window09=TOL Cards
Window10=RwyInfo
Eliminate each of the associated [windowsnn] sections and gauges listed.
Leave only the vcockpitnn sections.
Test for results.
Unfortunately I no longer have a gauge programmer and my skills are limited to panel creation basics with some mods capabilities.
I hope this helps.
EDIT: Attached is a modified panel.cfg zipped for testing.
A note from my dim memories as a Dash seven driver many years ago is that there is no gear or flap sound heard in the cockpit excepting a bot of a thump as the nose or mains lock into position up or down, perhaps a bit of wind noise and slight burble sound from the nose extended in flight. The hydraulic motors/pumps, which give the whine, are in the wing root area.
Very pleased to see interest in this somewhat rare and venerable product of Canada.
Cheers: Tom
Very pleased to see interest in this somewhat rare and venerable product of Canada.
Cheers: Tom
BendyFlyer
Charter Member
Milton, thanks a lot I will give this a run today and see what happens. Your feedback and assistance is appreciated.
I understand your issue about gauges. I have been working on a remake of Jens Kristensen's Shorts Hythe to make it back into a Shorts Sunderland, the gauges have been a real pain and I must confess designing them from scratch is beyond my skills but due to it being a 2004 port over some panels will stay as popups and alas Jens answers no emails so I guess we will just issue it and be done with it.
fliger747 - yep that was the same for the Dash 8 no noise except air noise and airflow changes when the gear doors opened and the thump as the gear locked down, given they have a common heritage and parts it is not surprising. The flap PTO on the ground could grind and groan occasionally and I always felt the Dash was distinctly agricultural compared to pure jets and some other turboprops like the King Air. The Dash 8 100 was no slouch at short fields either but nothing on the Dash 7 and while I saw a few around the traps never had a chance to fly in one. As a STOL driver and bush flyer basically all my flying career I wish I had had the chance to fly the 7, Milton's work makes up for it and I just can't get out of it, well except to try carrier landings in his Tracker and occasionally to reminisce with the 727. My award for the shortest landing yet though goes to the BN-2 which you could get down on the piano keys and turn off at the first taxiway at Broome (RWY 28) if you were really on top of the beast. I reckon if you dropped the Dash 7 into beta before touchdown and hit the brakes and reverse thrust simultaneously it would probably do the same!
I understand your issue about gauges. I have been working on a remake of Jens Kristensen's Shorts Hythe to make it back into a Shorts Sunderland, the gauges have been a real pain and I must confess designing them from scratch is beyond my skills but due to it being a 2004 port over some panels will stay as popups and alas Jens answers no emails so I guess we will just issue it and be done with it.
fliger747 - yep that was the same for the Dash 8 no noise except air noise and airflow changes when the gear doors opened and the thump as the gear locked down, given they have a common heritage and parts it is not surprising. The flap PTO on the ground could grind and groan occasionally and I always felt the Dash was distinctly agricultural compared to pure jets and some other turboprops like the King Air. The Dash 8 100 was no slouch at short fields either but nothing on the Dash 7 and while I saw a few around the traps never had a chance to fly in one. As a STOL driver and bush flyer basically all my flying career I wish I had had the chance to fly the 7, Milton's work makes up for it and I just can't get out of it, well except to try carrier landings in his Tracker and occasionally to reminisce with the 727. My award for the shortest landing yet though goes to the BN-2 which you could get down on the piano keys and turn off at the first taxiway at Broome (RWY 28) if you were really on top of the beast. I reckon if you dropped the Dash 7 into beta before touchdown and hit the brakes and reverse thrust simultaneously it would probably do the same!
BendyFlyer
Charter Member
Milton, thanks for the panel cfg. This appears to have resolved the conflicts re the 2D v VC control positions. I can get all 4 started via the manual start method, though I must admit as an ex turboprop driver not seeing an N1 rise before introducing fuel via the condition lever does catch me out but I can live with it. There does appear to be some mixup in the starter engine select switch logic now and then, i.e no. 2 Engine will start first not no.1 but they all catch eventually. I will ponder the coding for the switches in my spare time as well as the issue of the lag in the power reduction for prop power reduction after take off but I think it is probably an issue with my joystick and FSUIPC and not the modelling. One thing is for sure, nothing is ever straightforward with FSX, you get it right for one situation and start all over again with another.
BendyFlyer
Charter Member
Shockwave lights for the Dash
For those interested and able to use them here is the shockwave lights data for the Dash courtesy of the Aussie Flight Sim Forum OZX:
Just cut and paste replacing the current light data in the aircraft cfg file.
LIGHTS]
//Types: 1 – Beacon, 2 – Strobe, 3 – Navigation, 4 – Cockpit , 5 – Landing, 6 – Taxi, 7 – Recognition, 8 – Wing, 9 – Logo, 10 – Cabin
light.0=3, -1.9, -46.4, 3.6, fx_shockwave_navred_nl,
light.1=3, -1.9, 46.3, 3.6, fx_shockwave_navgre_nl,
light.2=2, -2.3, 46.4, 3.7, fx_shockwave_strobe_l_nl,
light.3=2, -2.3, -46.4, 3.7, fx_shockwave_strobe_l_nl_3,
light.4=1, -43.4, 0.2, 17.17, fx_shockwave_beaconh_l,
light.5=1, 5.35, 0.0, -7.60, fx_shockwave_beaconb_nl,
light.6=10, 9.00, 0.0, -3.0, Fx_D7cbn3 ,
light.7=10, 4.00, 0.0, -3.0, Fx_D7cbn2 ,
light.8=10, 0.00, 0.0, -3.0, Fx_D7cbn3 ,
light.9=10, -4.00, 0.0, -3.0, Fx_D7cbn2 ,
light.10=10, -9.00, 0.0, -3.0, Fx_D7cbn3 ,
light.11=10, -16.00, -1.0, -3.5, Fx_D7cbn2 ,
light.12=3, -46.1, 0.1, 1.2, fx_shockwave_navwhi_nl,
light.13=2, -44.8, 0.02, -0.85, fx_shockwave_strobe_l_nl_2,
//-------------- Landing Lights ------------
light.14=5, -1.40, -31.4, 1.10, fx_Shockwave_landing_light_tail ,
light.15=5, -1.40, 31.4, 1.10, fx_Shockwave_landing_light_tail ,
light.16=5, 1.00, -34.70, 2.65, fx_Shockwave_landing_light_tail ,
light.17=5, 1.00, 34.70, 2.65, fx_Shockwave_landing_light_tail ,
//--------------- Taxi Light --------------
light.18=6, 23.54, 0.00, -7.90, fx_shockwave_landing_light_small,
[smokesystem]
smoke.0= 10, -22.0, 1.5, fx_smoke_f6,
smoke.1= 12, -11.0, 1.0, fx_smoke_f6,
smoke.2= 12, 11.0, 1.0, fx_smoke_f6,
smoke.3= 10, 22.0, 1.5, fx_smoke_f6,
For those interested and able to use them here is the shockwave lights data for the Dash courtesy of the Aussie Flight Sim Forum OZX:
Just cut and paste replacing the current light data in the aircraft cfg file.
LIGHTS]
//Types: 1 – Beacon, 2 – Strobe, 3 – Navigation, 4 – Cockpit , 5 – Landing, 6 – Taxi, 7 – Recognition, 8 – Wing, 9 – Logo, 10 – Cabin
light.0=3, -1.9, -46.4, 3.6, fx_shockwave_navred_nl,
light.1=3, -1.9, 46.3, 3.6, fx_shockwave_navgre_nl,
light.2=2, -2.3, 46.4, 3.7, fx_shockwave_strobe_l_nl,
light.3=2, -2.3, -46.4, 3.7, fx_shockwave_strobe_l_nl_3,
light.4=1, -43.4, 0.2, 17.17, fx_shockwave_beaconh_l,
light.5=1, 5.35, 0.0, -7.60, fx_shockwave_beaconb_nl,
light.6=10, 9.00, 0.0, -3.0, Fx_D7cbn3 ,
light.7=10, 4.00, 0.0, -3.0, Fx_D7cbn2 ,
light.8=10, 0.00, 0.0, -3.0, Fx_D7cbn3 ,
light.9=10, -4.00, 0.0, -3.0, Fx_D7cbn2 ,
light.10=10, -9.00, 0.0, -3.0, Fx_D7cbn3 ,
light.11=10, -16.00, -1.0, -3.5, Fx_D7cbn2 ,
light.12=3, -46.1, 0.1, 1.2, fx_shockwave_navwhi_nl,
light.13=2, -44.8, 0.02, -0.85, fx_shockwave_strobe_l_nl_2,
//-------------- Landing Lights ------------
light.14=5, -1.40, -31.4, 1.10, fx_Shockwave_landing_light_tail ,
light.15=5, -1.40, 31.4, 1.10, fx_Shockwave_landing_light_tail ,
light.16=5, 1.00, -34.70, 2.65, fx_Shockwave_landing_light_tail ,
light.17=5, 1.00, 34.70, 2.65, fx_Shockwave_landing_light_tail ,
//--------------- Taxi Light --------------
light.18=6, 23.54, 0.00, -7.90, fx_shockwave_landing_light_small,
[smokesystem]
smoke.0= 10, -22.0, 1.5, fx_smoke_f6,
smoke.1= 12, -11.0, 1.0, fx_smoke_f6,
smoke.2= 12, 11.0, 1.0, fx_smoke_f6,
smoke.3= 10, 22.0, 1.5, fx_smoke_f6,
Bjoern
worst developer ever
Sorry to bump this one.
Here's a fixed engine starter for the Dash as the original code was valid for FS9, but suffered from K: var spam in FSX. This made the startup process terribly unreliable.
No more flickering annunciator lights and the starter will disengage automatically after ignition, so the engines will much sooner return to idle condition.
Either replace the entire content of panel\ST_Dash3 with the text here:
http://pastebin.com/DTitwk8f
Or download the attached text file, change the file extension to .xml and then overwrite the original file with it.
P.S:
Any bored painters out there who want to return the favor with
http://cdn-www.airliners.net/aviation-photos/photos/9/5/9/0643959.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/2/2/2/1400222.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/4/9/3/1021394.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/1/0/3/1949301.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/6/2/4/1896426.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/5/2/4/1896425.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/5/3/9/1421935.jpg
?
Here's a fixed engine starter for the Dash as the original code was valid for FS9, but suffered from K: var spam in FSX. This made the startup process terribly unreliable.
No more flickering annunciator lights and the starter will disengage automatically after ignition, so the engines will much sooner return to idle condition.
Either replace the entire content of panel\ST_Dash3 with the text here:
http://pastebin.com/DTitwk8f
Or download the attached text file, change the file extension to .xml and then overwrite the original file with it.
P.S:
Any bored painters out there who want to return the favor with
http://cdn-www.airliners.net/aviation-photos/photos/9/5/9/0643959.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/2/2/2/1400222.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/4/9/3/1021394.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/1/0/3/1949301.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/6/2/4/1896426.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/5/2/4/1896425.jpg or
http://cdn-www.airliners.net/aviation-photos/photos/5/3/9/1421935.jpg
?