freded

A couple of minor issues with the Phenom 100 and P3D v.3.35 After reinstalling this aircraft via Migration Tool (and being able to start the engines and have correct interior views), I have noticed the following:- 1. I keep seeing this message: "Flying Tip. Your fuel level is critically low in the selected tank. Automatic refill is available now. To complete this action, press: CTRL + X". Checking the fuel level on the MFD shows plenty of fuel - certainly not "critically low"! Not that important but irritatingly distracting... 2. When I open the GFD Mode Controller (Shift + 3) the window opens correctly but is completely nonfunctional. I've checked in FSX with the Phenom 100 and the GFD Mode Controller works perfectly. Has anyone else encountered this problem and (better still!) found the answer?

A couple of minor issues with the Phenom 100 and P3D v.3.35 After reinstalling this aircraft via Migration Tool (and being able to start the engines and have correct interior views), I have noticed the following:- 1. I keep seeing this message: "Flying Tip. Your fuel level is critically low in the selected tank. Automatic refill is available now. To complete this action, press: CTRL + X". Checking the fuel level on the MFD shows plenty of fuel - certainly not "critically low"! Not that important but irritatingly distracting... 2. When I open the GFD Mode Controller (Shift + 3) the window opens correctly but is completely nonfunctional. I've checked in FSX with the Phenom 100 and the GFD Mode Controller works perfectly. Has anyone else encountered this problem and (better still!) found the answer?

"I've tried using Migration Tool in an attempt to correct these faults but it doesn't help." Had a thought:- First uninstalled the Phenom 100, after backing up any changes I had made; then run Migration Tool & select 'Enable'; then reinstall the Phenom 100; next, port over the backed up changes. Now I can run the Phenom 100 in P3D v.3.3.5, a) without having transparent patches in the interior views and b) with the ability to start the engines. My mistake was failing to uninstall the Phenom prior to running Migration Tool. I hope all this is helpful to anyone else with a similar problem.

I've read all replies in the topic about P3D v.2 but, as I am running P3D v3.5.3, I wonder whether anyone knows if Carenado has plans to release the Phenom 100 for this newest version of P3D... The reason I ask is because I am encountering two serious problems . First and most frustrating is that, whatever I try, I cannot make the engines start. This is accompanied by a message saying that the chosen fuel tank is dangerously low - in spite of both tanks actually being full! The second problem is that, in the VC views, the cockpit walls around the panel are transparent and the exterior is as visible through them as it is through the windshield.This is also the case if I switch views to the passenger cabin. I've tried using Migration Tool in an attempt to correct these faults but it doesn't help. Seems to me that I must wait for Carenado to release an update that is compatible with P3D v3.5.3 Has anyone else managed to install the Phenom 100 successfully in this version of P3D? Correction: P3D v 3.3.5, NOT 3.5.3. :wub:

Hello Elaine, I finally tried rebooting the computer and now P3D is loading normally! BTW, where would I find that General Settings/Program that you mention - in case I need it later... Mark

It looks like I may have to reinstall P3D... Is there an optimal way to do this, without losing addons? Should I first backup, for example, the SimObjects folder and scenery.cfg? Thanks for any suggestions, Mark

Today, P3D fails to open with (occasionally) an error message referring to a .pnl file. Yesterday it opened normally. I have tried deleting these files, as recommended on this forum, but to no avail. I have also looked for any logs of errors but couldn't find any. Any ideas? Apart from a re-installation? Mark

Joe, Any luck with the COMM radio Issue? Regards,

In all other FS aircraft, when responding to an ATC request to change COMM frequency, the COM1 radio automatically tunes itself to the new setting. Not so in the MU 2B-60. But in spite of this, the new station is accessed and receives transmissions! Why is this and how can it happen if the COM1 frequency doesn't change? Puzzling! :smile:

I've re-run TTools.exe on all my AI traffic files - but still no AI in FSX on my Win 7-64 bit disk. Are 'Traffic_xxx.bgl' files compatible with Win 7-64 bit? Mark

All folders/files in SimObjects are the same - apart from some new additions to 'Airplanes'. Mark

Hi JUlian, No. All traffic_xxx.YYY files have .bgl as their extension. There is no file named 'trafficaircraft.bgl' or 'trafficAircraft.OFF' in FSX\scenery\world\scenery, but a search showed up 'trafficAircraft.bgl.BGD' ! I'll rename this to 'trafficAircraft.bgl' and see if that solves the problem. Watch this space! :smile2: Mark 'Fraid not... Still no AI traffic with the sliders set well up. Any other ideas? Mark

My apologies to any Italians I may have inadvertently offended! :rolleyes: Mark

Thanks for your replies. Doug: I have a dual booting setup (using the BIOS to choose which physical disk/OS is active). One disk has Win7-32 bit (my original setup); the other has Win7-64 bit (added later for FSX/P3D only). Devin: Yes. All of them. Steve: Here are the lines in the [Main] section of both the old 32 bit and new 64 bit FSG.cfg (they are identical):- [Main] User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc SimObjectPaths.6=SimObjects\AI Aircraft SimObjectPaths.7=SimObjects\CG AI Aircraft SimObjectPaths.8=SimObjects\CY AI Aircraft SimObjectPaths.9=SimObjects\GH AI Aircraft SimObjectPaths.10=SimObjects\HTAI Aircraft SimObjectPaths.11=SimObjects\MAIW Aircraft SimObjectPaths.12=SimObjects\PAI Aircraft SimObjectPaths.13=SimObjects\UGA AI Aircraft SimObjectPaths.14=SimObjects\WOAI Aircraft SimObjectPaths.15=SimObjects\###### Aircraft SimObjectPaths.16=SimObjects\ZZZ AI Aircraft Location=444,136,1476,904,\\.\DISPLAY1 HideMenuNormal=0 HideMenuFullscreen=1 ProcSpeed=3713 PerfBucket=7 Maximized=2 FIBER_FRAME_TIME_FRACTION=0.33 -should they be? Mark Correction! "SimObjectPaths.15=SimObjects\###### Aircraft" should be "SimObjectPaths.15=SimObjects\###### Aircraft"... Don't know how it got changed betwwen Ctrl-C and Ctrl-V !! Mark Whoa! The forum changed '######' to '######' again !! Why? Mark Why won't the forum accept 'W O P' (spaces added )? Mark

I have just installed FSX on a partition running Windows 7-64 bit. I transferred all the Traffic_xxx.bgl files from the FSX installation on my Win 7-32 bit disk to FSX\Scenery\World\Scenery on the 64-bit FSX installation, but no AI aircraft show up. Can anyone please explain what I am doing wrong? Mark

Thanks Michael! Why didn't I see that?! Mark

I'm flying the Tutorial 2 trip from EHAM to LOWI and all was going well until turning to 230 at AB. Then I had a problem following the instructions in the Tutorial. On page 118, it says:- "...Press DEP ARR and select the LOWI ARRIVALS page. Select Runway 08, which clears out the LOC/DME EAST procedure. We’re doing this because we don’t want the missed approach procedure for runway 26 to be in the FMC in the event of a go-around. This isn’t entirely realistic, but the Navigraph navdata does not contain a procedure for the circle to land’s missed approach. "Press LSK 3L to copy RW08 and then press LSK 1L to enter a direct to. Then enter the extended runway centerline course, 079 into the LSK 6R DIR INTC field. etc." Here is what the FMC shows me when I select the LOWI ARRIVALS page:- - which is OK. But when I take the next step, "Select Runway 08", instead of being able to "Press LSK 3L to copy RW08 and then press LSK 1L to enter a direct to." I get this page:- - which gives me a list of STARs on the left side. So there is nowhere at LSK3L to copy RW08 and enter a 'Direct To'. Do you think I've made an mistake somewhere previously that causes this error to occur? Perhaps I should go back to the saved flight,"Before top of descent" and try it again. :( Mark

Hi Glenn, Many thanks for your reply. I certainly DID read the Tutorial closely - I even selected passages and printed them so I had a readily available source to refer to during the set-up and flight. :-) I'm pretty certain I didn't confuse GW with MAX GW, as I compared the Tut. screen shot with my setting of the FMC and the difference was in the GW. As far as resetting the MCP altitude, I think I now understand that process - both for climbing and descending. Although I did have a serious problem when trying to descend to Schiphol: the A/T did not change the readout in the EICAS Engine window from CRZ to DESC. Consequently the throttles remained at the CRZ setting and in spite of deploying the SPD BRK (as requested by the FMC) it was impossible to descend fast enough. Then the FMC said "Descent point unachievable" - or words to that effect, so I performed a missed approach, circled, used Flight Planner to make a plan and used ATC's directions to make another approach. This worked and I was able to intercept the localiser and GS and made a successful CAT II (?) landing. Whew! So I still don't know why the A/T wouldn't change to its 'descend' setting and allow the engines to spool down. Any ideas? I had been careful to "RESET MCP ALTITUDE" to the suggested 2000 ft when indicated and the vertical path indicator appeared on the ND, so why didn't the throttles 'RETARD'? I think the 'speedtape jumping' was due to some bug in my computer as there shouldn't have been any turbulence. I'll have another go at Tutorial 1 when time is available. Perhaps this time I'll get everything right! :-) Thanks again for you input - it's very welcome. Cheers, Mark

Hi Rick, Your tip about FSUIPC is very helpful. I had no idea it was "known fault"! How often does this need to be done? Ryan asked me to delete FSUIPC.INI and let it be remade. This sorted out my problem... Cheers, Mark

Ryan, Well, that FSUIPC.INI was obviously corrupt! The present flight is now at cruising alt and speed and approaching REDFA on the route. So, barring any screw-ups by yours truly :rolleyes: , I should be able to complete the flight. I'll e-mail you both versions of the INI file, as requested. One point I should mention is that while setting up the FMC, I noticed on the PERF INIT page 1 that the GW (at LSK 1L) was showing as '168.0' instead of the '138.0' in Tut.1. As a result of this, TRIP/CRZ ALT (at LSK 1R) showed 'FL250/FL250' instead of 'FL301/FL250'. I decided to try correcting this (it had been the same error on previous flights but I had ignored it...) by line-selecting '138.0' into LSK 1L. This was accepted by the FMC. Another unexpected - to me ^_^ - message from the FMC was that, during the climb phase on LNAV & VNAV, a message appeared at the bottom of the screen telling me to reset the selected altitude. I had been under the impression that VNAV would do this automatically but apparently not. So I changed the value of 'Altitude' on the MCP to the next value on the LEGS page. Nothing happened until I clicked on LVL CHG and then VNAV, as soon as a positive climb was shown. Re-reading Tut.1, I now see that I should have expected this and used ALT INTV instead. One last point, while I have your ear: the speed tape in the PFD is 'jumping', by which I mean the tape itself is flicking up and back irregularly without affecting the indicated speed. Is this normal or do I have a video fault? Thanks for your help! Mark

Ryan, I have closed FSX, deleted FSUIPC.INI (making a back up of it, too) re-opened FSX and, having reconfigured the FMC for the Tut. 1 flight, am about to takeoff... I checked that FSUIPC has rebuilt its INI file - the new one is much smaller! So I'll report back when I see what happens with the flight. :-) Mark

'FlightWatch', Here's the latest screenie from my next attempt:_ And here are the shots of the FMC pages you asked for:- The Takeoff Ref page is not, of course, a shot of the setting before I started the flight. In fact I added Flaps 5 before taking this screenie to simulate the original. Trim was originally 5.04 and VR 142. Hope you can tell what's going on from all this... BTW, I did a complete uninstall/re-install yesterday, so can't think why it should be already 'corrupted'. Mark

PhotoBucket again... At last! Now if I can just remember what I did... Mark

Trying PhotoBucket now...

Another go at pasting images (from ImageShack):- These screenies were taken when flight was paused as mentioned in my post of yesterday at 2:36 PM Mark Those weren't big enough! How do I make them appear larger?