Jump to content

BiologicalNanobot

Does Just Flight DC-10 work on Prepar3D v5?

Recommended Posts

Posted (edited)

Dear @MammyJammy I dropped this lady many years ago (I was disappointed), but this tread caught my attention and I found your mod. What a game changer. Now installed in P3Dv5 and with button clicks etc. Great job. THANKS. 

I took her out for a spin today. Everything seems fine. I only had one thing which is perhaps just on my flying skills. The plane is sliding from right to left during climb. Perhaps @KrisJ has an idea about what it can be that cause this. Can't recall to have meet this behavior before in my long time as a simmer.

@KrisJ thank you for the flap settings. Will try this later tonight.

Jan

Edited by Lerbech

Share this post


Link to post
17 hours ago, Lerbech said:

I took her out for a spin today. Everything seems fine. I only had one thing which is perhaps just on my flying skills. The plane is sliding from right to left during climb. Perhaps @KrisJ has an idea about what it can be that cause this. Can't recall to have meet this behavior before in my long time as a simmer.

Assuming there is no bug in the software the only thing that come to my mind is too low speed and/or too high AoA getting close to stick shaker speed. Make sure you always have enough speed above minimum to ensure safe climb. After TO it is V2+10 at around 10 degree nose up and then you accellerate to 250kts or slats retraction manouvering whichever is higher. If you give me your TOW I can provide you proper flaps/ slats retraction schedule so you can verify it.

If it happens in sppeds much above minimum maybe its an autopilot issue? Does it happen with AP in lateral navigation mode (HDG or LNAV/ GPS)?

Share this post


Link to post

Thanks @krisJ. I was thinking that it could be the yaw damper, but I can't see any deflection on the rudder from the outside view. I don't think it's a bug in the AP as this wasn't engaged. Can be I'm not inside the flight envelope - TOW could be the issue, but she climbed nicely. I'll recheck my parameters and give it another go.

Thank you for the input.

 

Jan

Share this post


Link to post
On 3/10/2021 at 1:36 PM, Lerbech said:

Thanks @krisJ. I was thinking that it could be the yaw damper, but I can't see any deflection on the rudder from the outside view. I don't think it's a bug in the AP as this wasn't engaged. Can be I'm not inside the flight envelope - TOW could be the issue, but she climbed nicely. I'll recheck my parameters and give it another go.

Thank you for the input.

 

Jan

Solved. It was my Ezdok settings causing this strange behaviour. Everything is now fine and I just made a great landing at CYYZ. Thanks @MammyJammy for bringing this plane back in the air. Your work really increased the "flight fun factor".

Jan

Share this post


Link to post

I need to change Ctrl+Shift+F12 assignment to something different as it interrupts with GSX when I fly FSLabs Airbus. Airbus is trying to call GSX using Ctrl+Shift+F12 assignment and instead it calls DC-10 panel configs... Any advice how can I change it to for example Ctrl+F12 assignment?

Share this post


Link to post
14 minutes ago, KrisJ said:

I need to change Ctrl+Shift+F12 assignment to something different as it interrupts with GSX when I fly FSLabs Airbus. Airbus is trying to call GSX using Ctrl+Shift+F12 assignment and instead it calls DC-10 panel configs... Any advice how can I change it to for example Ctrl+F12 assignment?

Go to P3D Add-On menu and under GSX you can change your key assigment. I use Ctrl+Shift+Tab+F12. Hope it helps.

Share this post


Link to post
41 minutes ago, Samaritano said:

Go to P3D Add-On menu and under GSX you can change your key assigment. I use Ctrl+Shift+Tab+F12. Hope it helps.

That wont help. Its GSX which must stay with Ctrl+Shift+F12 as other addons refer to this assignement when calling GSX - FSLabs for example. Thats why its DC10 panel congigs assignement which I need to change.

Share this post


Link to post
2 hours ago, KrisJ said:

I need to change Ctrl+Shift+F12 assignment to something different as it interrupts with GSX when I fly FSLabs Airbus. Airbus is trying to call GSX using Ctrl+Shift+F12 assignment and instead it calls DC-10 panel configs... Any advice how can I change it to for example Ctrl+F12 assignment?

The key combo for the panel states is in the Lua file that enables panel states for the DC-10.  Go to your FSUIPC Modules folder and open the file DC10PnlState.lua.  The last line in that file controls the key assignment for the panel states.  It should read:

event.key(123, 11, "displayPanelStatesMenu") -- Ctrl-Shift-F12

You can change it to whatever you want.  The first number, 123, is associated with the function key used.  You can set it to Ctrl-Shift-F10 by changing that number to 121.  Pages 19 and 20 of the FSUIPC for Advanced Users.pdf (in your FSUIPC docs folder) has the listing of key codes you can use.  The second number (11) determines the modifiers for the key combo.  In this case, 11 is Ctrl + Shift.

When I have time I will circle back on the annoying issue with the doors and the FE panel annunciators for them.  It's a royal pain and I haven't been super-motivated to deal with it.  I will also fold in the flap updates and a few other tweaks in the next batch of updates.

Share this post


Link to post
Posted (edited)
2 hours ago, KrisJ said:

That wont help. Its GSX which must stay with Ctrl+Shift+F12 as other addons refer to this assignement when calling GSX - FSLabs for example. Thats why its DC10 panel congigs assignement which I need to change.

For me it works. I have Ctrl + F12 for my GSX menu and Ctrl + Shft + Tab +F12 for "you control" and Ctrl + Shft + F12 for Panel States on the DC-10.

My KeyMapping.ini located on C:\Users\YourUsername\AppData\Roaming\Virtuali shows the following.

[common]
youcontrol=Ctrl+F12
[GSX]
shortcut=Shift+Ctrl+Tab+F12

 

Edited by Samaritano

Share this post


Link to post
On 4/13/2021 at 7:34 PM, MammyJammy said:

The key combo for the panel states is in the Lua file that enables panel states for the DC-10.  Go to your FSUIPC Modules folder and open the file DC10PnlState.lua.  The last line in that file controls the key assignment for the panel states.  It should read:


event.key(123, 11, "displayPanelStatesMenu") -- Ctrl-Shift-F12

You can change it to whatever you want.  The first number, 123, is associated with the function key used.  You can set it to Ctrl-Shift-F10 by changing that number to 121.  Pages 19 and 20 of the FSUIPC for Advanced Users.pdf (in your FSUIPC docs folder) has the listing of key codes you can use.  The second number (11) determines the modifiers for the key combo.  In this case, 11 is Ctrl + Shift.

When I have time I will circle back on the annoying issue with the doors and the FE panel annunciators for them.  It's a royal pain and I haven't been super-motivated to deal with it.  I will also fold in the flap updates and a few other tweaks in the next batch of updates.

Thanks! Works fine now.

Share this post


Link to post

MammyJammy - If others have not said it I will again, thank you for your endeavours and hard work on this, it is truly appreciated.

I think you have done a remarkable job in dragging the CLS DC-10 into the modern sim environment. Your howto guide is comprehensive and once followed through you end up with a first rate sim experience with the DC10. I have surrendered a lot of my earlier mods for this one in preference to yours which really take this one to another level. I can also say that after countless hours of trying to mod the airfiles etc that the SGA folk had it nailed in the first place and it is the only way to get this one flying like a 10 should. The 10 is no longer a 'Lite' model but a high quality simulation experience. 

ZJeMloX.jpg

 

 

 

  • Like 2

Share this post


Link to post

@MammyJammy - firstly thank you so much for your work on this aircraft and bringing it alive.

Today on finals I saw a number of messages appearing relating to the callout files and also when starting the APU. I wonder if you know what the issue might be with this?

For example:

"Error encountered
the wait operation timed out

Full Error Code 0x102
location 5
File c:\users\myname\Documents\Prepar3D v4 Add-ons\JustflightDC-10\Guages\PanelSounds/dc10cls/APU_START.WAV"

I checked in that folder and the filename(s) it referenced are there.

Edited by jjf
Typo

Share this post


Link to post
On 5/9/2021 at 12:42 AM, jjf said:

File c:\users\myname\Documents\Prepar3D v4 Add-ons\JustflightDC-10\Guages\PanelSounds/dc10cls/APU_START.WAV"

Are you sure the path is correct?  You have a typo in your path for the folder name "Gauges".

That error is generated from the sound gauge itself, not any of the Lua scripts to support the DC-10 mods.  The only time I have seen this error is when the path or file name is incorrect.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    47%
    $11,790.00 of $25,000.00 Donate Now
×
×
  • Create New...