-
Drive c is pretty full
Also, changing registry entries will not be enough... You also need to modify every line in every parameter files used by FSX or add-ons where the drive letter is written. Exemple : inside fsx.cfg (for modules path), inside planes config files, etc... Could be a very time-consuming, trial and error work in order to not forget anything...
-
Everyone else really successful with FSX in Win 10?
Short update to my previous message about successful migration to Win10 ; Did a long range flight this week-end : 11 hours without acceleration or pause, from Rio de Janeiro to Paris Charles de Gaulle, in Pmdg 777/200, with following configuration : - FSX , DX10 Scenery Fixer + NVidia Inspector + EZDok - Orbix FTX Global + FTX Vectors + FTX Global OpenLC Europe + REX4 Texture Direct - Active Sky Next - Pro ATC-X - Professional Flight Planner X - Paris Photo HD scenery, Paris LFPG Mega Airport scenery Absolutely no problem.
-
Navigraph opinions
If you fly offline (ie not with VATSIM or IVAO) and don't mind having an outdated navigation data, you can just buy a one time update. You will have up to date/accurate nav data for this month, and the data will just slowly become a bit inaccurate every month, but at least all you add-ons (FMC from PMDG, flight planners, ATC, ...) will use the same data, based upon your month of subscription/update. You only need a yearly subscription if : 1) you want to fly online because online ATC will use freshly updated nav data or 2) you want to fly the most recently updated sid/stars/routes. I just bought a 1-time (1 month) suscription in August, allowing me to update my nav data for : Pmdg 737 and 777, Aerosoft Airbus, PRO ATC-X, and PFPX. All those add-ons now share the same nav-data. Chris
-
Everyone else really successful with FSX in Win 10?
Hello all, A recap of my own experience about Windows 10 migration. Installed Win 10 Pro from Win 8.1 Pro on July, 29. Install went with no problem and system is working fine. My hardware config : - CPU : Intel I7 4790K - GPU : Asus STRIX GTX980 - RAM : 16 Gb - Disk Drives : - Win 10 on 1st SSD - FSX on 2nd SSD - Add-ons that does not need to be inside FSX folder are on a Hard Disk Drive (3 Tb 7200) - Screen : 27" / 2560*1440 - HOTAS Warthog + Saitek Pro Flight Rudder pedals I did have a few problems with my FSX install : all was working fine at start but I had multiples crashes to desktop after 10-30 minutes flying, that never occured before. As the settings were untouched (exemple : HIGHMEMFIX=1 in fsx.cfg, an UIAutomation Core.dll in install dir), I had no clues about what was the problem. I decided to completely uninstall and reinstall FSX and all add-ons from scratch on my new Win 10 system. Took me a while. The main add-ons that I am using are : - FSX Gold - DX10 Scenery Fixer + NVidia Inspector - Orbix FTX Global + FTX Vectors + FTX Global OpenLC Europe - REX4 Texture Direct - Active Sky Next - Pro ATC-X - Professional Flight Planner X - FSCaptain - EZDok - Aerosoft Airbus - PMDG 737, 777/200 & /300 - several payware and freeware large airports As said, the full reinstall was a lenghty process... Most/all of the tricks of a good install on others systems were used (HIGHMEMFIX, UIAutomationCore, DX10 SceneryFixer for DX10 Preview, changing several parameters inside fsx.cfg, installing with admin rights and setting FSX.exe with Admin Privileges, ...) but the result was worth it. I now have a fully functionnal FSX with all add-ons reinstalled and working nicely. I blocked framerate at 30 with high-end AA settings in FSX/DX10Fixer/NVI, and result is very smooth (probably not different from what I had previously on Win 8.1). Only problem remaining so far : Mouse Wheel zoom is not working correctly or not working at all, depending on which setting I use inside FSX, EZDok, FSUIPC. Still need to work on that, I am not totally sure it is Win 10-related, maybe I fumbled with the settings... In summary, I am quite happy with FSX on Win 10 so far, no compatibility problem for me. Chris
-
DX10 Fixer released!
Bought, downloaded and installed this morning just before leaving home to work... As a long time DX10-only user, I already use Steve's free patch and know which add-ons I own that have problems. Just made a very quick test before shutting down home PC. - MegaAirport Munich EDDM is working (no more grey buildings at dusk/night/dawn, and no more grey airport vehicles). - FTXGlobal vector lights are working (I renamed back the disabled texture file) - Skiathos X (Aerosoft 29Palms) is working (no more black boxes for night lights, same as FTXG problem I guess). So far it's a big thumb up, I still need to test a lot of other add-ons... A bit disappointed if FT/Dubai is not totally working, hope for a fix from FlyTampa side... Chris
-
Lufthansa has ordered 34 B777-9x today!
Hi, seems that Lufthansa is still quite Airbus-oriented if you look at the current fleet : http://www.airfleets.fr/flottecie/Lufthansa.htm (column "active") Besides 32 B737 and 31 B747 (+18 MD 11), the remaining of the 313 airplanes fleet is only Airbus (including 10 A380). The B777-9 delivery will increases a bit Boeing share but if you add the 25 A350-9, balance is still heavily on Airbus side... Chris
-
New post from Steve on his WordPress site...
Can't wait also Flying with DX10 exclusively since many months, but the Fixer should solve my last gripes with this mode : many airport add-ons "grey buildings or vehicles" and light fixing, FTX Global black boxes lights, ... I will at least be able to use night flying without most (or any) problems still arising today...
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
Thanks guys for your comments ! Well... In fact I had a crash just a few seconds before landing... I just did a short flight Seattle to CYVR to take the last pictures of the flight. When the crash occured I did not research the cause and I am not sure it was an OOM. I almost never have crashes with FSX since months, and never had since this flight (but I did not do long flights (no more than 2 hours) since this LFPG-CYVR flight). Since then I have read many posts about possible OOM problems with 777 and I will investigate that. My next long range flight is scheduled for this week-end. For my next mid/long range flight tomorrow (probably a Vienna-Dubaï, I own both airport add-ons), I will use Process Explorer to survey the VAS value. Chris
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
A few more pics borrowed from the hard disk, from the same flight : Overflying EGGL (Heathrow) among scattered cloud layer : Greenland snow everywhere : Northern Canada :
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
Thanks for your link to this map :rolleyes: I was parked at gate 2 if I remember well... Chris
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
Hello You could be right. I am not familiar with this airport and the definition of différent gates is not given in my FSDreamteam CYVR manual... When I activated GSX after landing and chose a gate, I did it at random :blush:
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
Thanks for your comments ^_^ Talek, FPS vary a lot depending on several factors, of course. I am using a quite high screen definition (2560x1440) with mostly hign end settings for FSX, and Paris CDG is not very framerate-friendly (compared to some other large airports). But i also use Ulitmate Traffic 2 with 50% traffic load, and it means a lot of planes in or around CDG. You can see the FPS counter on most of the pics (large yellow number on top right corner). Near LFPG, numbers are ranging from 26 to 10 FPS (10 inside cockpit at entry of runway, looking towards the busy airport area). Most of the time, I have between 15 to 25 FPS around CDG...
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
Ground control asks us to park at a Terminal A gate on the other side of the airport. Being not very familiar with the area, we ask for a Follow Me car. After some minutes of taxi around the aiport, we eventually reach Terminal A and our parking gate. Ground crew and vehicles are ready to take care of the plane. After last turn, we slowly get close to the parking signal, trying both to not overrun the stop line and to be as much aligned as possible. 5:17 PM French time, 8:17 AM Vancouver time. Cabin crew is managing the exit of passengers towards the arrival area of the airport. Passengers will be a bit tired today, they arrived more or less at the same time they departed France (-9 hours shift between time zones) ! While the pilot and FO are busy shutting down the main systems, catering ground crew handle the cargo and passengers luggage. This concludes our Paris - Vancouver flight. I hope you enjoyed the ride on Air France (PMDG)777-200 and will be happy to welcome you on a next travel B) Chris
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
Our plane is now ready for landing, approaching minimums with full flaps. I will do a manual landing, so I disconnect auto-pilot while leaving auto-throttle enabled. Mount Baker can be seen behind the plane. The tail view below allow us to see Richmond suburbs below the plane, the northern arm of Frazer river above the right wing, and Vancouver Intl airport and 26R directly in front. Nice view on the bay behind. View from the cockpit on short final. doing a last correction to the path towards the runway. Altitude is a bit higher than optimal glide path but nothing serious. Almost there... Passengers can spot the different airport areas, parking lots, and the traffic of other aircraft on parking and taxiways. The cockpit crew is still busy landing the plane but with a near perfect attitude and glide slope and low (9 knots) frontal wind, this is quite easy. Touchdown ! After 9 hours and 31 minutes, we land at Vancouver International airport. Spoilers and brakes are used automatically and pilot commands the reversers, as seen from the cabin. Post 8 : Vancouver
-
Air France 777-200 (PMDG) : Paris LFPG -> Vancouver CYVR
We have contact with CYVR approach and we will be vectored towards runway 26R (funny, same exact runway heading as the one we departed from at Paris Charles de Gaulle) Runway, flaps setting and ILS are entered on the CDU. Encountered a bug (I think) with an error message on the screen about incorrect rwy/ils frequency. Found the solution on PMDG forum (thanks to Pause function during the flight) : need to erase the frequency M line on the CDU RAD/NAV page and all went well afterwards. Starting turn towards the runway under guidance of ATC. First levels of flaps are already down and speed is rapidly decreasing. Now on the ILS glide, speed is low enough to lower the landing gear as we pass nearby a golf course in a residential suburb (FTX Global). Post 7 : Landing Post 8 : Vancouver