ckovoor

About

Username
ckovoor
Joined
Visits
1,110
Last Active
Roles
Member

Comments

  • @q400sim Thank you for confirming that you can use the alternate Standalone version in P3D4.5. I am happy that you find it useful.
  • > @RayS said: > Just installed the gauge and XMLTools as required. Checked the entry is in DLL.XML and all is same as documentation. > I am running P3DV4.5 and it's not showing the correct calculations, as screenshot. > Thanks,…
  • > @RayS said: > I am running P3DV4.5 and it's not showing the correct calculations, as screenshot. > If you are running P3Dv4.5, you should be using the Standalone Gauge, see here: http://majesticsoftware.com/forums/discussion/…
  • @Doc_Z said: I found it on the vehicle, instrument panel list and checked it. It does not appear. Is the .jpg that was included in the original download supposed to be used anywhere? As I do not myself use P3D, I cannot guide you any fur…
  • > @Doc_Z said: > I have installed the gauge as per the instructions, but when I check it on the drop-down list, it doesn't appear. Where should it be? If you are using P3D, then you might find some useful information about opening the …
  • Why not look around the COMMUNITY MODs Section to consider other alternatives: majesticsoftware.com/forums/categories/community-mods
  • @Doc_Z said: Is your version 1.7 compatible with P3d v5 or 5.1? This version of the gauge, which is dependent on the concurrent installation of XMLTOOLS64, will not presently work in P3Dv5 or 5.1. This is because the incompatibility betwe…
  • It was discovered that the current version of the gauge is not clearly visible at dusk/night, so I have uploaded a new version 1.7SA which can be seen clearly in a dark cockpit as well: https://dropbox.com/sh/9l8rrmxm34vtlnl/AADk5o45oJE5buJV_wvdRV4…
  • It was discovered that the current version of the gauge is not clearly visible at dusk/night, so I have uploaded a new version 1.7 which can be seen clearly in a dark cockpit as well: https://dropbox.com/sh/tnftcge1093owlz/AADkVjRy7zdm-RK-OnrBvcv-a…
  • @airwolf66 said: Hello, after installing the Standalone V-Speed Calculator and Setter I can't find a way to open the program. Is there a hotspot or a key combination? There is no "hotspot". If you are using P3D, then you might find …
  • I have uploaded an updated version 1.6 of the V-Speed Gauge at: https://dropbox.com/sh/ly3vz0dohpj7bt9/AAD12m9lMAc3XSr69H1zVg7Ma?dl=0 This new version rectifies an error made earlier on the temperature range applied ("at or below 20 C") in the…
  • @Alti : Did you use the updated dll of XMLTools64 from: https://fsdeveloper.com/forum/attachments/xmltools64-zip.40019/ ? I just want to cross-check with you, and also find if any others using the Gauge in P3Dv5-HF2 are experiencing the same issues,…
  • Oops, I got it mixed up above: VoiceMacro and audio-router are to be started before the Q400 is loaded, for problem-free operation. I have also created alternative voice-interactive checklists based on the Challenge-and-Response items of the orig…
  • Appropos my post above in which I reported that audio-router seems to interfere with the Q400 sounds, I subsequently found that if Voice Macro and audio-router are started AFTER the Q400 has fully loaded with its sounds operational, there is no inte…
  • Additional Note (5) On my version of the MJC8 Q400 running on FSX-SP2 and Win7 x64, if I use the audio-router program to route the PNF's (Windows TTS) voice to my headphones (default communications device), then the cockpit sounds from the Q400 are …
  • I should point out that 2 distinct utilities have been referred to in this thread. The original subject matter of this thread is a LUA Script created by Chris Warner back in 2014, which is still available at the FSUIPC product support forum at: …
  • @niksan29 said: Now the only problem with flaps is 5, there are no speeds for them: https://i.ibb.co/fGWPCvq/vreff.jpg No, nothing can be done about this....these speeds (Vref for Flaps 5) are missing from the tables in the AOM as …
  • Looking at the T/O-Climb table for Vclimb, I realized that Vclimb for Approach-Landing can be obtained from the same table, because it is solely a function of Aircraft Mass, which is known at all times. So it was an easy matter to amend the code to …
  • @niksan29 said: probably because: http://majesticsoftware.com/forums/discussion/509/mjc8-q400-landing-speeds-card-incomplete-data#latest The Majestic Speeds Card is, I believe, only a summary or extraction from the Tables presented in…
  • @niksan29 said: @ckovoor said: Your observations about the position and colour of the Vref bug are not, of course, related to the V-speed gauge. Why? if possible, just swap these bugs. First Vref(filled\black triang…
  • @niksan29 said: FCOM said: https://i.ibb.co/PgM669w/vref.jpg Have a good look at Table 19.6 you have referenced from FCOM 2.19.15 ..... you will see that the increment is +15 knots against Flaps 35.
  • @niksan29 said: But why 15 knots ?! It should be 20, everywhere it says 20, I don’t know where you got 15 knots from ... As I had mentioned in an earlier post, the 15 knots correction is taken from an actual hard-copy Q400 AOM, which I …
  • I have amended the code to include the new instruction: "-- if icing conditions and Flaps 35 add 15 kts to Vref and check some flap selected to avoid increasing numbers if ICING pressed alone --" and have uploaded version 1.3 of the gauge to the D…
  • @niksan29 said: noticed a small problem, does not add + 20 to Vref (only flap 35), when icing button pressed Thanks for pointing this out. Now, the Majestic Landing Speeds Card says: "When flying in icing conditions, Add 20 kts to Va…
  • @niksan29 said: made a mini comparison for flaps 5 with a similar script but running on Lua Script (in FSUIPC) http://majesticsoftware.com/forums/discussion/494/majestic-q400-v-speed-calculator- and-setter#latest As you can …