Main ini´s are not created on custom liverys. Any tips how to solve this. P3dV5 and Training version

Best regards

Patric

Sound will work from loading a flight up to 15 to 60 minutes in. At some point, all sound WILL cut out and nothing will be left. No main and no headphones playback. The DASH-8 will be completely silent and nothing can be done to bring back any sound. There is nothing in particular that triggers it, it happens in random situations at random times. On the shortest of trips I might get lucky and get on the ground before I lose sound, other times it disappears before I've even started up an engine.
This is really a problem. Without sound there's no joy in flying the aircraft at all. I've spent the past four days trying to troubleshoot this and it's extremely frustrating at this point.

It may be a Navigraph issue, but regarding RJOO TIGER2 Departure, there seems to be a problem with the route to TIGER when flying from Runway 32L/R.
Could you please investigate this as I am attaching the documentation regarding CDU and Chart?　

Runway 32L/R Procudure:
Climb RWY HDG to 500FT or above, turn left within 4NM from RWY end/ITE 2.1DME, via ITE R201 until crossing YOE R301 turn right to intercept and proceed via YOE R291 to TIGER.
Cross TIGER at or above 6000FT.

RJOO Runway 32L/R to TIGER route.

TIGER to SOUJA route.

FMS Route Selection

Please refer to images, but TIGER has been removed and changed to go almost directly to SUMAR.
Is this a bug or a Navigraph issue?
Is it normal?
I'd be happy to get more details.

RW13L FAHA2B FAHAZ DCT KEROP DCT TISAK DCT OKLOP DCT RAXAD DCT MAKED P36 ALIKO ALIK2F LGTS/16

I completed the FP in the normal way so, selected LHBP, then found the downloaded route. I completed the departure as FP and then the arrival into LGTS. Having selected the landing RW, then finally ILS21R there was an option to go via D342J. If I selected this, the freeze immediately happened. If I did not, no freeze. I can reproduce the freeze every time when D342J is selected.

I mention this only for info of developers and in the event colleagues encounter a similar problem. I cannot recall ever having this issue. The next flight I did with all waypoint in the FMC caused no issue. I suspect it is an isolated issue linked to one STAR? I have both payware for the airports.

Best,

Keith

https://i.imgur.com/Wg3zKC1.jpg
[https://i.imgur.com/fk5ko7E.jpg

It's the first time I've noticed this, cant say for certain it was there prior to 1.025 update (which I'm running)

Just wanted to share another of those nauseating Flight Sim time wasting issues.

I have the Pro Edition with the Visual Extension pack (VDP)recently purchased (excellent by the way). Initially all was well, then suddenly yesterday, once airbourne my flight deck view went totally red. (see image.) However, the external views were fine as you can see. Whatever I tired failed. I use chase plane. I only have/had this issue with the Dash. So, you know what's coming! The investigation begins with suspect checking. What have I done recently. Well, nothing that comes to mind. My Pro version is up to date. The Nvidia card is up to date. System up to date. P3Dv5.2 all good. Could it be the VDP, so uninstall the Dash and reinstall without the VDP. No joy still red. So reinstalled the VDP. So maybe Chase Plane bearing in mind only issue with the Dash. I verified the files with Orbx. I setup the flight deck again in Chase Plane and this seems to have done the trick, three flights without incident.
All very odd. I will update with any change. Would welcome comments from members who may have experience the same or ideas etc.

Regards,

Keith

My friend and I are experiencing a weird bug regarding sound.

I hadn't flown the MJCQ4 for a while, and after some weeks, I thought it would be a good day to fly the Dash8, but after I loaded into my flight sim, I heard no sounds, and I did nothing to the plane.

Kind regards,
Samuel

I have the Training edition of the Majestic Q400 for P3DV5.3 with the most recent hotfix, and I just installed the cargo/freighter version of the Q400 and flew from CYUL to KLGA, and noticed that the landing lights aren't dynamic like they are on the normal passenger version of the Q400.

Is there some way to fix this?

Thanks

CPAN settings:

• Timing source = Multimedia Timer (else = Queue Timer: The clocks runs half speed only.)
• FDE to FSX Sync = Disable (... or was this one causing the clock running half speed?)
• Graphics refresh rate = Medium (not likely to have impact on this)

Seems a minor bug to me.

am I mistaken, or is the calculated distance DIST on the PERF page too high?

Cf. the other thread
majesticsoftware.com/forums/discussion/1338/p3dv5-3-mjc8-400training1-024x64-fms-flight-plan-dist-on-perf-page-too-high#latest

I only speak from my fligh sim experience regarding other FMSes, ie. 717, 737, 777, 747.

All disregard the legs behind the destination runway, I guess in order to check, if the timetable STA can be kept, and that the Landing Fuel calculations are still correct, or within margins. Their PERF INIT pages offer the RESERVE Field, which serves to input the expected Landing Fuel.

Any Dash8 pilots around?
Or the Majestic staff?

Thanks in advance.
Pecker

I do not recall ever not hearing the autopilot disconnect sound. But, it appears that something has changed with the 1.024 version. I now find the autopilot disconnect sound to be intermittent; sometimes working and other times, not working (no sound upon disconnect).

I am wondering if this is a bug which may have been introduced in the 1.024 version, or correct behaviour in the real aicraft depending on how the autopilot is disconnected (ie, if you use the disconnect button on the yoke versus the AP push button on the aircraft's front panel)?

For reference, P3D is set up with the default "Z" key, under keyboard commands, for autopliot disconnect. I have also set, again within P3D, my joystick's fire button for a single press (no repeats) to disconnect the autopilot. I do not use FSUIPC for keyboard or joystick commands.

Pressing the fire button on my joystick has worked flawlessly for years, in all aircraft, to disconnect the autopilot ... as has pressing the "Z" key on my keyboard ... PMDG, Aerosoft, Flight1, A2A, FSLabs and Majestic. A disconnect sound has always played in each and every aircraft, including the Majestic Dash 8. But, since installing the 1.024 version, the disconnect sound now appears to be intermittent in the Dash 8.

I am also using the 125Hz controls, so I wondered if I should edit the ini file and add a joystick disconnect parameter in there. I previously had only the ailerons, elevators and rudder set to use 125Hz. So I did that, adding J2_b0=AFCS_->inputs.AP_disengage to the [JOYSTICK_INTERFACE_ASSIGNMENTS] of the ini file.

I thought that had fixed it. With testing, in flight, the autopilot disconnect sound did play when I pressed the fire button on my joystick. However, on the same flight, I also noticed that if I press the "Z" key on my keyboard, no disconnect sound played. Interesting. So I am wondering now if the autopilot disconnect button on the yoke (which would be activated in the sim by using the J2_b0=AFCS_->inputs.AP_disengage line in the ini file) causes the sound to be played in the real aircraft, but pushing/toggling the AP button on the front panel does not cause the sound to be played in the real aircraft?

However, on my last flight, despite thinking I may have solved it by adding J2_b0=AFCS_->inputs.AP_disengage to the ini file and the autopilot disconnect sound working during the cruise section of the flight, it suddenly did not work as expected. I was on final approach and wanted to hand fly the landing, I pressed my joystick's fire button, the autpilot disconnected, but the disconnect sound did not play. So why did it work in cruise, and not on finals? Is there perhaps some kind of wierd conflict occuring with my having three separate places set up for the sim to disconnect the autopilot ... the 125Hz J2_b0=AFCS_->inputs.AP_disengage in my ini file, the "Z" key within P3D's keyboard commands, and also my joystick's fire button within P3D?

I am sorry for the long explanation, but the playing or not playing of this sound does appear to be a bit intermittent for me and I think a full explanation of my setup, as well as my actions, will be helpful in possibly getting a good response to my question. There seems to be no "pattern" to when it works or not.

In short, does the autpilot disconnect sound always play for other users, every time ... or, has something perhaps changed in the 1.024 version to "correct" the behaviour of this sound as per the real aircraft (for example, in the real aircraft does the sound only play when the yoke button is pushed as opposed to when the AP push button on the front panel is pushed?) ... and/or, is there possibly a conflict with how I have three separate places in my sim configured as autopilot disconnect possibilities?

I am hoping Kroswynd or other users can shed some light on this for me.

Whenever the taxi light is on, the brightness of the HGS maxes out - this didn't happen with my previous installation. Is this a known bug with a known fix?

Thanks for any help!

As I had a bit of problems with P3dv5, maybe due to so many addons or Win 10 updates, I uninstall and reinstall everything with Admin rights.

Prepar3dv5.13.28131
MJC Q400 Pro 1.021 64 with the 125 Hz - CPAN Multimedia
Only stock airports
Driver Nvidia updated 427.29
Active Sky P3D
Aviaworx for the FMS
Navigraph FMS only

I have also MFSF 2020 on that computer. I wont comment on that one. Does not look quite ready yet for the Q400.

No other program installed as the computer is only for Sim.

My problem: I cannot set the altitude, nor the V/S; it goes up and back to "0" for the V/S and to any altitude never above 2000 Ft when trying to set the altitude. This is the same on the ground or in the air unless I pause the Sim.

I uninstalled and reinstalled few times P3d and the MJC Q400 with the same result.

Thank you if you have an idea as it is not very simple to work the Q400 that way and I am starting the Aerosoft Arouind the World in 80 days managing my first leg EGKK to LFPB with great difficulties.

Kind regards,

JP

When i selected Flaps 10 sundenly the aircraft become out of control and the time/season goes to night. The location changed sudenly from i was about to land to somewhere in the middle of the pacific ocean.

What is going on?...

I have discovered a new and interesting bug. After landing, I called up the GSX menu to request parking services. As soon as GSX loaded in, the Q400 engines shutdown. And by this I mean, the condition levers remained at max and of course the pullfueloff handles were in, but the engines simply spooled down. I should add I had a couple 1000lbs still in the fuel tanks. I tried to restart, but even though the starter engages, the Nh begins to rise and the Np turns slowly, the fuel flow never exceeds zero and the engine will not start. Has anybody seen this before? I will look at the FSDT forum as well. Thanks!

After trying two shared cockpit flights with two different users , I was using Training version and the others PRo Version , I've identified one issue that the altimeters settings were not synchronized.

For example when I set 1005hPA, the other user reads 1009 hPA , if the other user sets 1001 hPA, I read 1007 hPA.

May you please try to replicate and try to identify what is the source of this issue?

Kind Regards

I do have new Baboo livery.

I use P3Dv4.5 on Widows 10

Regards

The way I have my joysticks setup, the Honeycomb Alpha yoke was "joystick 8" in the windows order (J8 in the ini file) when I was assigning axis's in my mjc84.ini file. I could not get the ailerons or elevators to move in the Q400 with the Honeycomb Alpha as Joystick #8 (J8). I eventually unplugged all of my joysticks, and plugged them back in. This time my CH Products rudder pedals were in joystick #8 and the Honeycomb Yoke found itself as J2. The ailerons and elevator moved, but now the rudder pedals stopped working. I unplugged everything once again, and got both the rudder pedals and yoke out of joystick #8 (J8) and they are now in J2 and J7, respectively.

So this leads me to believe that 125hz controls configured via the mjc84.ini will not work when you are trying to use a joystick in position #8 (J8). Is this by design or something that needs to be ironed out?

Thanks!

Any advice?
Thanks,
Alessandro

This happens mostly (it seems) at the gate. I bought P3D v.5.1 and the 64 bits Q400 version for it yesterday.
I first had the hydraulics/oil temps abnormal readings, tried uninstalling and reinstalling a few times before discovering the fix on the download page. My bad. Then this. I could not find anything here regarding this problem. I don't have addons installed and not planning on using much apart from P3DWX and maybe eventually a world texture pack. I installed with admin rights. I just use Windows Defender at the moment. I run Win 10 home 64. Quite reluctant to reinstall as I only have 2 installs left on day 2 of owning the plane and the sim. Thank you in advance for your help.