Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

429 profile views
  1. Thanks for the input. Right now I am worried as to the security of the pgm files. After installing I got a security warning that I had "TrojanGenericKD.42825397" in my system and I had to back everything to an earlier HD backup in order to get rid of it. I can't be sure that it came from OBS Studio, howerer, it is a possibility. John
  2. I have just downloaded the OBS Studio and followed the quickstart instructions. I run P3Dv4.5 under Winsows 10. I started the sim in the default scenario and in its own window, ran OBS and pressed start recording, left it for a minute and then stoped the recording. The screen was black all the time, however, there seemed to be sound recorded. How do I get the sim image into OBS?
  3. I repeated my flight ESSA/ENGM today and noted the following. After departing ESSA and passing TL I set my pressure to 1000 hpa instead to 1013. My descent clearance into ENGM to FL70 worked without repeated requests to descend immediately to FL70. I was then cleared to FL45. This was also accepted by ATC. The TL is FL70 so would have expected to be cleared to an altitude and not a FL. I was subsequently cleared to FL35 for the approach but chose to set local pressure Q0981 and this did not cause any problems presumeably because I was close to the localisor and glide path. There are inaccuracies in all this but I understand how to handle it and it is manageable. When I have time I can tinker with FSUIPC but it is really out of my depth to do this! John
  4. Did a new flight ESSA-ENGM and was cleared down to FL 70 but had to stop at 7200 in order to satisfy ATC. I was then clears to FL45 - note not altitude 4500 inspite of the TL of 7000. Again I had to stop att 4800 in order to satisfy ATC. I was then cleared to altitude 3500 and using local pressure found that this worked. I need to repeat this flight in order to confirm the above.
  5. I ran the Orbx Global Vector auto configuration after installing Mega's ENGM and reindexed Vox but forgot to choose apply. I have done this again and did a flight ESMQ-ESSA. My altitude instructions worked so now I have to test ENGM just to make sure all is well.
  6. Hi jabloom! Good to hear from you again. We had a long discussion concerning fatal errors on approaching ENGM which I initially hoped you had fixed with an adjusted bgl file. Unfortunately, there were other problems I had not noticed - my EFB was not giving me the ILS frequencies for landing. In the end I decided to bite the bullet and invest in Mega Airports version of ENGM. Some one down the line had suggested that it was the best solution. It fixed everything with the exception of this altutude problem and since I have been having the same problem with ESSA there must be a more global background to the question. I ran the Orbx Global Vector auto configuration and reindexed Vox but this did not help. Your thoughts.... John
  7. A number of years ago I bought the Q400 Cadet tutorial and more recently the Amsterdam Tutorial. I was then able to log into the Airline2Sim webpage and from there access the Aurasim app. I now find I have a problem with this. After starting the app I clicking on System (Aurasim1.png), I can see that my subscription is active and until further notice. When I click on Performance (Aurasim2), however, I am told that my membership is no longer active and consequently the function is not available to me. Can someone comment on this and perhaps solve the impass. I enclose the information shown by the app. Could it have something to do with running Aurasim on a remote and not on the sim computer? Aurasim1 & 2 John
  8. As stated above: Where: ESSA - ENGM, approaching ESBA I am asked to descent to FL90. Shortly after levelling I am asked repeatedly to "descent immediately to FL90". My solution was to gradually continue descending at 100 ft intervals until ATC was satisfied (8,500 ft) and stopped calling for an immediate descent. The other scenario (ESMQ-ESSA) was after descending to the requested FL I was asked to climb immediately to that FL. In this case I continued to climb at 100 ft intervals until ATC was satisfied (FL+600ft).
  9. I run P3D4.5 under Windows 10 and have just started flying the Q400 again after many months on the PMDG NGXu. I have Orbx Global scenery and the 2001 Navgraph Cycle installed. Also Active Sky and VoxATC 7.42. On my two first flights I have been given clearances to descent to a lower flight level (pressure is STD 1013hp) for my approach, however, when I get there Vox continues to pester me with "...descend immediately to FL XX". I tried changing to local pressure as given by Active Sky but this did not help. Then I did a stepwise descent to FL XX - 100, -200, etc and at -600 Vox seemed to be satisfied and stopped its transmissions. This has happenned at both airports in question - in the later case I was asked to climb to the assigned altitude and did a similar stepwise ascent to FL XX +100, +200 etc until Vox was satisfied. Anyone out there with an idea of what is going on here. John
  10. I run FSiPanel v3.4 under P3Dv4.5 and Windows 10. I have recently installed the latest update of the Q400 (1.20b) and have a problem similar to the above. I cannot figure out what I am missing. Any suggestions?
  11. I have started migrating my addons from the P3D Core to an Addons Folder according to Mike Davies and wonder if the is a way of doing this with my aircraft: PMDG NGXu Majestic Q400 Any ideas?
  12. I followed your instructions for all three GND frequencies but to no avail. I suspect that this is not a problem we can solve. Thanks anyway. John
  13. Since my last reply I removed all additiional frequencies (files included in link above) and copied the new bgl over the existing one for all runways, ran the indexer and tried a new start at EHAM. The result was the same as before. I then edited the GND frequency to 121.80 thinking that the previous 121.70 was the problem. I also changed my Gate at EHAM. This did not help either and VOX still asked for 121.70. I don't understand this since I had limited my choices for GND to 121.80. Do I have to do these edits in all the runway options? (there are five: All, East, West, North and South). John
  14. I have checked my Navgraph comms data against the ADE-list-comms data for EHAM and don't see anything untoward there other than som frequencies are designated .015 in Navgraph and .020 in ADE. I didn't remove or change anything and enclose the .bgl file for your perusal. It is in my Dropbox and you will find it using the following link: https://www.dropbox.com/sh/hk7vqg5rer63g9d/AADj1PPXC3F4aflceBQWbM6xa?dl=0 I did a new test run with Vox from EHAM Gate D3 and all runways open. It was as follows: Tune to ATIS on 122.200 Tune to CLD on 121.980 Tune to GND on 121.700 (Navgraph .705) The above gave me a FATAL ERROR and garbled (repeated) replys from ATC Hope you see something. Maybe remove the extra frequencies as a test? John
  • Create New...