Boss
About
- Username
- Boss
- Joined
- Visits
- 157
- Last Active
- Roles
- Member, Administrator, Moderator
Comments
-
They are not simulated, since we do not have a real light effect for these lights. They are essentially bogus lights
-
As Kroswynd mentioned, we've never seen this problem before, and it is very difficult to imagine any reason why Q400 might have this kind of behavior. You could do something like J0_X=FlightControls_->sensors.BrakeL0 J0_Y=FlightControls_-&…
-
@aua668 You could try running MJC84 System Panel at the same time. It also uses UDP interface from the Q400. Check the electrical page of the System Panel while your CDU does not update. See if the changes in the cockpit are reflected on the syspa…
-
@Struggle_Crow said: I think a bug fix for the FMS feature is a priority. We can't select Enroute Transition with SID/STAR Runway selection. and FMS 1/2 synchronization is needed. When it's done, please publish the API to allow users…
-
@dustingrantham said: I fly the Q400 for real. Biggest request from me is enhanced VNAV capability in the FMS. In the actual aircraft the FMS will calculate a VNAV path based on a pilot set glide path angle eg. 3 degrees or whatever you choose. T…
-
Please contact support@majesticsoftware.com for assistance regarding this issue
-
Since this is an isolated issue, may I ask you to contact support@majesticsoftware.com for assistance Thank you
-
@Maarp Can you please confirm the gear handle is up, but the gear still does not move ? Could you possibly attach a screenshot ? One thing I could think of is that there was a gear system malfunction which was later saved into a situation file…
-
The Universal 1E simulation of the MJC Q400 is using the Navigraph database as follows. From the FAF to MAP the altitude are set according to those published in the database exactly. When the approach course co-insides with the runway heading one wi…
-
The following info on VNAV limitations might be useful * If the runway is not on approach path (offset path), one can not use the FMS 3D approach for the final approach leg. Either one should switch to the ILS, or fly the leg visually * Ofte…
-
@RichW could you please contact support@majesticsoftware.com about this issue. Thank you
-
@daredevil There weren't any changes at all to the graphics from version 1.020. Would you be able to check that 1. The black rectangle is present on each popup window 2. Would be present as well with electrics off ? My suspicion is that some …
-
Could it be the FSUIPC utility which is set to periodically save the situation ?
-
@p3dx3 could you please try to set an fps limit on your p3d, and see if this makes a difference ? There a bug in the p3d that when fps is unlimited the mouse clicks might be delayed
-
Thank you for your report. As this seem to be an isolated issue, could you please contact support@majesticsoftware.com ?
-
@Yoda1976 Unfortunately the crashes with Prepar3D V4.x became more common, we think it has to do either with updates of the sim, or updates of Windows * Do you possibly have The Win10 2004 update installed ? * Could you check if setting Win7C…
-
If anyone wants to help resolving the issue, please check if Q400 has generated a fresh CMJC84BaseErr.log file in the Prepar3D v5 client root folder. If it is there, we kindly ask you to email it to support@majesticsoftware.com
-
@korundar for the reset, please contact support@majesticsoftware.com with your order number
-
The jumping hydraulic pressure and the unrealistic oil figures are the signs of the failure in the copy protection system of the Q400 We think a windows update is responsible for this behavior. If you experience this problem, please manually eras…
-
Thank you for sharing this information with us. The effects are not included, as they are no longer needed with new dynamic lights we have implemented. The next patch will address the issue of the sim logging this error
-
@somiller thank you for letting us know. Can you please tell us which company is the developer of the KSEA scenery ?
-
@notarealpilot is Q400 your default aircraft ? If so, may I suggest you don't load it as default, as it is not a good idea with any addon aircraft
-
Unfortunately I can not reproduce this issue on the development PC, however may I ask that all users having this problem attempt to delete any existing situations with the Q400, especially any of the .mj1 or .mj2 files found in the situation folder …
-
It seems like a Chaseplane issue, so I would suggest contacting their support. Q400 does not include any functionality which would change the view as you move the mouse
-
Until the issue is fixed, please only operate the APU switches via VC or via 2D panel, do not mix both
-
Thank you. Yes, unfortunately the old forum user database could not be restored properly. You have done correctly by registering in the new forum
-
check if fsuipc automatic saving of the situation might be active. It will cause stutters with Q400