Ken Hall

Thanks, Alex... on my next visit to Spain I will try the alternate 115.90 you mention and see what happens. I have a subscription to Navigraph so always have the bang-up-to-date data there but the P3D data could well be the 'culprit'. As previously stated "not hugely important" - curiosity satisfied 😎.

W10, P3D5.3, LNM_2507: Good morning Alex. I have been flying in and out of Spain a number of times recently using VOR to VOR in my flight plan. I note that changing frequency to tune BLV (Bilbao) on 117.65 it does not indicate as DME (distance) although it shows as a waypoint. Any ideas why? Not hugely important - just curious! Ken.

Good morning, Alex... Disabled UT2 and the 'problem' appeared to be rectified. However, the skies were like a desert and looked a very lonely place 😪 I have reinstated UT2 and will run LNM with the user a/c displaying the type and xpdr number - that works every time. Thanks for your input. Ken H.

Happy New Year, Alex. Running: W10, P3Dv5.3+, LNM 32-bit v3.0.12, AIRAC 24/13. On start-up and loading LNM flight plan I can see my aircraft I.D. as Skyways/1142 + Actual Alt + Alt above ground. However, the underlined detail, for some unknown reason, will change quite randomly to some other ID as in today's flight chganging to 'Hansaline/9999'. I have tried all sorts of alterations within various settings wihout removing this 'annoying' random change! As an experiment toiday I went to Tools/Options/User A/c and ticked all available boxes - applied the changes and was able to see on the map, my aircraft with every 'ticked' box visible but with the incorrect ID 'Hansaline/9999'. I have no idea where this incorrecrt detail is coming from. The aircraft.cfg is shown below with items I really want to see in bold text: [fltsim.0] title=Fly UK A321-231 IAE Crystal G-FLIB sim=AirbusA321-IAE-ProjectAirbus model=IAE panel= sound=IAE texture=flyuk_Crystal_v1.0 kb_checklists=AirbusA321_check kb_reference=AirbusA321_ref atc_id=G-FLIB atc_airline=SKYWAYS //atc_heavy=0 atc_flight_number=1142 atc_parking_types=GATE,RAMP atc_parking_codes=UKV ui_manufacturer=Fly UK ui_type=A321 Crystal ui_variation=Fly UK VA ui_typerole=Commercial Airliner ui_createdby=Fly UK visual_damage=1 The only possibility I can think of is that within my Sim I also run UT2 which I have used since its inception and there is possibly a 'Hansaline' entry although I have not checked. That said, I have also had incorrect airlines shown as Emirates; BA, KLM and others. The same/similar issue arises irrespective of which aircraft is being flown so is not only the one detialed above. Can you offer any solution(s) to correct this anomaly? Very strange indeed! Ken H.

Sorted ~~~ reply from another forum ~~~ the UT2 XML file was still pointing to C:\~~Steam instead of D:\FSX...I knew it had to bwe something simple - just not that simple For your info ~~~ all sliders at MAX except for Water at low 2x... Now that UT2 is enabled the frames have dipped a bit but still 30+ at EGLL...ASNext and FSCommander running and all across three video outlets. But thanks for your input...

I foolishly allowed FSX-SE to install to C:\ on my recent new system - that 250GB SSD became almost full (92%) so I have created a link (cmd menu in W10) and transferred ALL the FSX contents to a 1TB drive D:\. Everything is working 100% - except for UT2 On the FSX-SE startup screen I am not presented with the "Ultimate Traffic initialised" sound file and a permissions request. I have uninstalled UT2 several times now and each time reinstalled (boxed DVD version) UT2 to the D:\FSX\Flight One Software\UT2 - run the setup as administrator - run the configurator and set the calendar etc, etc...even run the gamut of the utii.dll "quarantined" etc. What I find is that having uninstalled and reinstalled I am never asked for the serial number. I guess there is something still lurking in the registry. I have since run the uninstall through "Revo Uninstaller" which then identifies remnants of files hiding in the system which I then remove ~~~ still can't make UT2 show me any traffic and as stated above, on the FSX-SE startup screen I am not presented with the "Ultimate Traffic initialised" sound file - checked in the config sequence. Some general assistance would be appreciated - especially with regard to any registry entries. The registry is somewhere I would not venture under normal circumstances - especially as I'm not sure where I should be looking and what I should be looking for... Other than that - the "link" has given frame rates a massive boost and is running at 120+ with only a drop to 60+ at Heathrow Xtreme... I have used UT since its inception then UT2 ~~~ really, really desperate to have it back ~~~ otherwise I might have to resort to FSX default traffic

Hi Guys, well ~~~ all does appear to be OK I ran the Makerwys file again and it DID run through every airport on the system at a tremendous speed... Made some deletions and rebooted the system ran RC database and just the instant windows as described in my first post. Added some more airports and again ran the DB with same "instant" results... Made a trial flight from Leeds to Southend and experienced a (new for me!) severe congestion (or words to that effect) and was taken on a real roller-coaster scenic excursion until the controller message "bring 'em in" Everything worked fine so I guess it is all OK... What I have learned is that (unlike my long and happy relationship with XP) I HAVE to right-click and run as Administrator to ensure it all comes together. Just running the exe from a desktop shortcut I find that some bits work and some bits (same software) don't !!! W10 is taking some "getting used to"... Thanks again. Ken

Thanks, Ray... I was just "afraid" that it was not working correctly because it was not trawling through the many hundreds of files that usually zip past in the progress bar Maybe it is a result of upgrading to this new mega-quick PC ? I remember buying my very first electronic calculator - never believed it could possibly work as quick as it did and so spent just many hours checking the calculations the long way with pencil and paper... Similarly, I was visiting my son and downloaded an item to my Tablet..(nothing happened) ...again, again, again...to find I had multiple copies of the same item and all because he has Super Fast Fibre and (at the time) mine at home was 2.8 MB/s on a good day... Teknolergy, huh! Ken

Thanks for your interest... The path is correct - I was initially telling RC to look at */*/*/common/FSX but that only resulted in an error message. When I left off the FSX bit it ran straight away! Since running the first DB session after installation it took some time to read all the bgl's etc. I have since installed UK2000 Leeds; Stansted; Edinburgh and Southend plus a shed-load of ORBX freeware airports for Europe and the USA... I would have expected some attention to the new files installed :( Ken

HI Guys... recently took delivery of a new PC and am running W10 with FSX-Steam Edition... Installed FSUIPC v4.949 (latest and full version); installed MakeRunways v4.692. So far so good... After installing RC (new Reg Key arrived in about twn minutes!!!) I ran the database which went through OK. Having installed some new scenery and airports I am trying to run the DB again - but - it does not seem to be playing ball What I see is the following pop-up windows: Is this a wideFS - NO enter path to FS: C:/Program Files (x86)/Steam/steamapps/common (accepts this OK) then: RC rebuilding r4.csv / running MakeRunways.exe Finished rebuilding r4.csv RC rebuilding new a4.csv file RC finished rebuilding a4csv At that stage nothing further happens - previously it would have run through the entire system checking airfield files... Any comments - or am I missing something. Don't understand why RC would run the DB on the first attempt but not since! I can confirm that each time I open ANY files I right-click and "Run as administrator"... Ken

Good morning Ray, I think that we can out this one to bed now Changed my start-up to the default Cessna with "no weather"...this gives me a STD 1013.2 at 680' when at LeedsBfd. I then relocated to LEAL and then changed aircraft to the POSKY 737-700 - still 1013.2 at 140' - correct for LEAL... After loading the fltpln ASN kicks in and the STD pressure immediately changed to 1039mb / 30.68" but still at 140'... Made the flight with RC and everything just went ticketyboo - being very careful to monitor pressure using the FSUIPC/16 figure (it maintained 16211 right down to final FL120) - at 39.8 DME I received the approach details :rolleyes: So success again... Thanks again for your time. Ken

Ray and Ron ~~~ thanks both for your input on this issue. Time is a prescious commodity and I appreciate your generosity with yours I am going to change my FSX start-up to a default Cessna with "no weather", STD pressure and will load ASN afterwards. Ray ~~~ my STD pressure buttons measured the correct 1013.2 using the offset/16 so it is working correctly. I will report back up after this next round of checks and hopefully this topic can then be "resolved". Thanks again. Ken

Sorted :wub: First I will respond to your questions above... When I press STD on either the panel or my GF module it does return 1013.2 ~~~ I have been using RC for years (7 or 8) - never had any issues (apart from learning not to change altimeter when first told and wait for "descend TO **** feet") The RC display shows 40 miles then at 39 came the words Only been experiencing this issue for a few days... So...I deleted the aircraft - rebooted the PC - installed the aircraft again ~~ same. Installed FSUIPC (update) 4.938f ~~~ same. Stern measures...recovered a back-up of RC from my "vaults" ~~~ took ages... But it all works again Now ~~~ I made this last trial flight with ASN disabled but at FSX start-up it still showed Alt as 1000mb but at correct height (141) at LEAL. I would have thought that with NO weather the standard 1013.2 would have been showing??? On running RC and taking the WX brief he also told me QNH 1000... I am wondering if saving a flight for start-up with Std QNH set at 1013.2 at 680 feet at LBA would be a safe bet although I have not been able to set that up as yet - can't seem to make it work (is ASN still making the rules here despite being "disabled"? Your comments most welcome but thanks anyway for your assistance and patience :blush: Ken

Ray ~~~ still a work in progress... I did have different deviation settings in RC: altitude was at 500 ft which I had set due to the ups and downs caused by REX weather engine. I have now changed back to the default "300" as I am now using ASNext. I have checked the sim on ground at start-up which is at LeedsBradford - alt 680ft. When I boot-up then switch on the avionics the altimeter is showing 1000mb / 29.53" with 680 feet on the display. Pressing the button assigned to STD changes the setting to 1013.2mb / 29.2" with an altitude of 1080 ft so it would seem that the buttons are working as they should. I also set the FSUIPC Logging Tab as you described - it says that up to four items can be displayed... I already had an entry for checking the virtual memory (just in case!). Entering your details (OK) did not display on the bar - not even after re-booting FSX. I deleted my previous entry and substituted yours and the number came up as 16002 which is as near as makes no difference the 1000mb as shown on my GF unit and the panel. I have not yet made a flight to check possible variations at altitude but I suspect that will not be an issue (?). The aircraft I am using - almost every flight - is a POSKY 737-700 with panel aliased to the default 737-800. I have used this configuration for a few years and everything worked fine! I do note that my FSUIPC is behind the times at v4.931 so I will update that today. Nothing else to report but will stay in touch. Many thanks for your input...do not wish to oustay my welcome Ken

Ray ~~~ aircraft is a freeware POSKY 737-700 with the default FSX-737-800 panel. I use a rack of GF modules and Pressure is adjusted via these - all alterations are reflected in the panel MFD when made. So, yes, Std pressure is confirmed in the GF module and also the MFD. Yes, I meant FL120 (just indicating altitude numbers in the GF- MCPPRO)... The only change has been the ASN uninstall (per instructions) and the installation of the update FSX_B5410. Have just repeated the last flight - after updating the RC database (just in case!). Exactly the same...instructed to descend from cruise FL250 to FL190 then FL120 within 30 miles. Descent rate set at 2000 fpm - started this descent at 68 miles out - reached FL120 at 46 miles out... At 39 miles out "missed crossing..." The previous flight was a descent from FL140 to FL120 ~~~ this time FL190 to FL120 ~~~ but still achieved well within the 30 mile limit! I also do not see any option to "unable" :wub: I aborted the flight :angry: My RC4 is v4.3.3845 which has worked flawlessly for years and which I recommend to all and sundry. Maybe I should reinstall RC... :huh: Appreciate your input B) Ken :blush: