il88pp

Thanks Pat! Sorry 'bout the rude awakening.:) il.

Found Pat explaining more. Here, post #10. https://www.flightsim.com/vbfs/showthread.php?291899-FSX-carriers/page2

I think for steam there is: Aicarriers.net (and aicarriers.exe may not work, but not sure on that.) user PhantomTweak knows more.:D

Do you mean spinning, and shooting up in the air, when you click the starter? That happens if you use slew mode before starting. If not, try describing it a bit better. Your "spazzing" doesn't tell me much.

panels re: shift 1, shift 2, etc not: control F1 etc.

Just a thought. You could try using a external dvd drive perhaps. One that you connects to Usb. The error messages seem to indicate a bigger issue though. Some kind of windows issue.

Sometimes DVD burning software can cause a conflict. My burning software, P2G8, would make the disk spin in the drive for over two hours. Then the sound would stop, and I could install fsx. As soon as I stopped the softwarefrom starting automatically with the pc, the problem was gone. (I can still burn a CD just fine, only difference is it used to offer to burn a cd when one was inserted, now I have to manually start the program. I actually prefer this.) Another way would be to uninstall the burning software, then install fsx, and afterwards install your burning software again.

Can

Tried once more, accidentally forgot to set up fuel, so it was still full fuel. Lifted off as well. Needed every inch of runway, but then, up up and away. That was flaps full. Tried full fuel at flaps 5 as well. No chance.

I set up weather, from interweb: temp:68F Dewpoint 17F wind 16 knots from 341 left press at sea level at 29.92 17.00pm local Default 747_400 fsx Acc. (fully default, not even panel edits, restored from backup for the occasion) Fuel 44% in each tank Set up AP: hdg-341 vs-600 alt-21.000 Flaps-Full trim up:-16 clicks Speed in autothrottle set to 159 Kias parking brake on thrust 60% for a minute, to warm up engine engaged alt hold and hdg hold. Ap not yet engaged. engaged autothrust. speed hold not engaged yet. Released parking brake, set full 'throttle'. at 3/4 runway, 120 knots, AP engaged (climb set.) when climb established, and speed above 130, speed hold engaged. result! But, at 55% fuel it hit the fence.

I'll give it a go. But what amount fuel did you use? Full fuel? Also, what was air temp and air pressure like?

I was looking for something and just came across this again. I saw it before but never used it. (I actually had it stored on my pc already.) == Partition Find and Mount == A Windows program that finds lost files on drives with lost partitions. Less steps then using systemrescueCD. And may be plenty for what you want to do. http://findandmount.com/

I had a usb die on me. In windows it was nort recognised, no 'poing' when plugging in, nothing. Then I booted the PC with sysrescueCD in the drive. (It is a linux OS with lots of tools. Nothing gets installed on ypur PC, it runs from a CD or flash drive.) I let it scan all drives, the USB was there! Scanned all drives again. This time it looked ok. I then 'mounted' the drive (required to make it accessible). And started the file explorer in sysrescueCD. Saw all files. Plugged in a second, empty USB stick. (Could have just used My harddisk instead, but t was only 2Gb data) Mounted that drive as well. Used the file explorer to copy everything to the drive that was ok. Done. The files were back. But the broken drive still was not recognised in Windows. I satrted SystemrescueCD again. I started the utility GParted in systemrescueCD. (Tool for formatting and Partitioning.) The USB was visible in GParted just fine. Selected the broken USB drive. Chose "Format" then Apply. ----->Still did not work in WIndows. Started SystemRescueCD again. Again GParted. Looked around for other options. Selected the usb drive. Chose: "Repair Boot Sector" (or create new boot sector or something.) (And then "Apply all operations" again) --->Booted into Windows. Usb stick worked again. No issue ! Was a nice 16 Gb Usb3.0 stick too. Was a very happy chappy. Have a look at my post 13 in this thread: https://www.flightsim.com/vbfs/showthread.php?292234-Windows-10-couldn-t-be-installed-We-couldn-t-update-the-system-reserved-partition/page2 especially the command you need to mount. It's in the additional tips part, below the lines: ------------------------------------------------------------------------------------------------------------------------------------------------------------------ **about /dev/sda1 All it is is a mount point for devices. dev stands for device. A way for linux to acces them. etc etc..

Did you get them? If not, have a read through my first guide in the thread about the system reserved partition. Directly below tip thread now. Do get some rest first though. But if you did not get your files yet, don't throw the stick away.

I think it will be hard to use one computers display as a display for another one. But I'm not sure. If you can find a cheap screen, I think you will save a lot of trouble. Not only getting it going, but also setting it up every time you use it. There are some programs for fsx that you can run on a second computer. For some of then you need to install simconnect on your second computer also. It's in the sdk files on the dvd. You connect the computer to the fsx pc and the programs connect to fsx. I think there are gauges/panels, others are like controllers, like an autopilot. Or weather programs, possibly with radar. That would be an option. But again it would take some settin up. If you use such addons now, running those addons on a second computer could give your pc a little breathing room.

I have no laptop, and never looked at this, but I ting it won't be easy. The issue is, the laptop monitor gets power from the laptop, through the battery. Not directly from the mains. The only way to switch that monitor on is to boot up the laptop. (i assume) So you would have to connect, and then claim the monitor, leaving the laptop os without a display. It seems unlikely to me. I think I would rather buy a 5 dollar monitor then break my head on it.

I recently wanted a cheap monitor. I went to a local thrift store. Turned out they had about 20 to choose from. I picked out a 21.5" 1440x9something widescreen, they wanted the equivalent of 7$ up for it, which I thought was a sweet deal. They even gave a 7day cool down period. :) It had only a vga input. I hooked it up, it worked, and still does well. For me that was an improvement over my 17" 1024x786. It's probably smaller then what you are used to, but if you just want to put instruments on a second screen it should be ok.

Glad to help out Jim.:) il88pp.

Update: Here 4 more handy buttons you can add to your default FSX Boeing 747 Virtual Cockpit. I will post the complete fix again, with the 4 new gauges at the bottom. The first 20 gauges the same as I posted earlier. The 4 new buttons/gauges (gauge 21, 22, 23, 24 ) are disabled in this code. To enable, remove the " // " before the gauges you want to use. Before editing, first make a backup copy of the Original B747_400 panel.cfg file. Then you can replace the [VCockpit01] -section with this one. It will give the autopilot (CMD) button and the backcourse (BC) buttons, as explained in post #8 Plus 4 more buttons. -Full/Exp -Pitot Heat (on/off) -Battery (on/off) -Kneeboard Icon [VCockpit01] size_mm=512,512 pixel_size=512,512 texture=$747_1 background_color=0,0,0 gauge00=Boeing747-400!Standby Altimeter, 0, 113, 111, 101 gauge01=Boeing747-400!Standby Airspeed Indicator, 112, 114, 111, 110 gauge02=Boeing747-400!Standby Attitude Indicator, 113, 1, 111, 111 gauge03=Boeing747-400!Primary Flight Display, 6, 234, 243, 267 gauge04=Boeing747-400!Multi-Function Display, 286, 259, 224, 252 gauge05=Boeing747-400!Clock, 1, 1, 113, 113 gauge06=Boeing747-400!EICAS Display, 286, 2, 224, 252 gauge07=Magnetic_Compass!Magnetic-Compass,225, 166, 60, 59 gauge08=Boeing747-400!Autopilot IAS-Mach Window, 233, 0, 45, 15 gauge09=Boeing747-400!Autopilot VS Window, 226, 15, 59, 16 gauge10=Boeing747-400!Autopilot Heading Window, 233, 31, 45, 15 gauge11=Boeing747-400!Autopilot Altitude Window, 226, 47, 59, 16 gauge12=Boeing747-400!Autopilot Hdg Switch, 259, 253, 25, 29 gauge13=Boeing747-400!Autopilot Localizer Switch, 256, 90, 29, 29 //is BC button - moved to VS spot, (BC button spot was orig: 256, 64, 29, 30) //gauge13=Boeing747-400!Autopilot Localizer Switch, 256, 64, 29, 30 //switched off, orig line for BC button gauge14=Boeing747-400!Autopilot Approach Switch, 226, 96, 29, 29 //gauge15=Boeing747-400!Autopilot VS Switch,256, 96, 29, 29 //switched off, orig VS, use Altitude-hold instead, location is now BC button. gauge16=Boeing747-400!Autopilot Nav Switch, 226, 126, 29, 29 gauge17=Boeing747-400!Autopilot IAS-Mach Switch, 256, 126, 29, 30 gauge18=Boeing747-400!Autopilot Speed Switch, 257, 285, 29, 29 gauge19=Boeing747-400!Autopilot Altitude Hold Switch, 226, 64, 29, 30 gauge20=Boeing747-400!Autopilot Master Switch, 259, 67, 25, 24 //autopilot-master switch (CMD), moved, is orig position BC button. //gauge20=Boeing747-400!Autopilot Master Switch, 259, 227, 25, 24 //switched off, Orig AP master spot. - There this button does not show up! //--Add these lines to your [VCockpit01] -section in your 747_400 aircraft.cfg file. //--To enable these next four VCockpit buttons remove the // in front of their lines. //--The buttons will appear in the 747 just above the PFD (Primary Flight Display). //--Some of these Gauges/Buttons are inside "Beech_Baron.cab". This file is already in //--folder ..Microsoft Flight Simulator X/Gauges and the gauges will be found there automatically. //--There is no need to add the "Beech_Baron.cab" to the 747_400 folder. //gauge21=Boeing747-400!Nav Display Switch, 166,249,20,40 //added, is B747_400 full-exp switch, in top of PFD //gauge22=Beech_Baron!Pitot Icing Switch, 206,240,16,32 //added Beech_Baron pitot heat sw, in top of PFD. //gauge23=Beech_Baron!Battery Switch, 50, 248, 21,27 //added Beech_Baron Battery Switch, in top of PFD. //gauge24=SimIcons!Kneeboard Icon, 90, 254, 20, 20 //added B747_400 Kneeboard Icon, in top of PFD. The vertical position of these last 4 gauges is around 248. That is the second number after the gauge. The first number is the horizontal position. If you want to move these 4 gauges around, to move them a bit to the left or right, you can edit that first number. Best to make small changes. Making the first number larger moves the gauge to the right. Making it smaller moves the gauge to the left. The last two numbers (not always there) determine the size of the gauge/button. If you move the button to far to the right or left it will be hidden behind the edges of the dashboard. Enjoy your default fsx boeing 747 Cockpit, il88pp It should look like this with gauges 21-24 all enabeled:

Oh, and at what point do you get the error message?

What did you install? The fsnd cockpit? My edits? ... A plane?

That was easier to find then I expected. Here you have my FSX 747 autopilot fix, for the default Boeing 747 VC. With this, you will get the buttons working in the 3D virtual cockpit in the default B747_400 for FSX. It should fix your 747 autopilot not working issue. This code is part of the panel.cfg file. For safety, make a backup copy of your panel.cfg file and name it: "panel -0- orig copy.cfg". just leave that in the panel folder, with the panel.cfg file that is used by fsx. Then open the panel.cfg file. scroll down untill you find the [VCockpit01] section. You can simply replace that section with what I posted here, or make the changes one at a time by hand. As you prefer. This will add the Autopilot-Master Button (Cmd) and the BackCourse button (BC). The Vertical-Speed button will be gone, but you don't need that. You can use the Altitude-hold instead. They do the same thing in this plane. Also gone will be the LOC button, but you won't miss that either. During an approach you can use the Approach button (App) which will also follow the localiser. During a cruise on GPS you will be using the Navigation button (Nav). Enjoy! il88pp. [VCockpit01] size_mm=512,512 pixel_size=512,512 texture=$747_1 background_color=0,0,0 gauge00=Boeing747-400!Standby Altimeter, 0, 113, 111, 101 gauge01=Boeing747-400!Standby Airspeed Indicator, 112, 114, 111, 110 gauge02=Boeing747-400!Standby Attitude Indicator, 113, 1, 111, 111 gauge03=Boeing747-400!Primary Flight Display, 6, 234, 243, 267 gauge04=Boeing747-400!Multi-Function Display, 286, 259, 224, 252 gauge05=Boeing747-400!Clock, 1, 1, 113, 113 gauge06=Boeing747-400!EICAS Display, 286, 2, 224, 252 gauge07=Magnetic_Compass!Magnetic-Compass,225, 166, 60, 59 gauge08=Boeing747-400!Autopilot IAS-Mach Window, 233, 0, 45, 15 gauge09=Boeing747-400!Autopilot VS Window, 226, 15, 59, 16 gauge10=Boeing747-400!Autopilot Heading Window, 233, 31, 45, 15 gauge11=Boeing747-400!Autopilot Altitude Window, 226, 47, 59, 16 gauge12=Boeing747-400!Autopilot Hdg Switch, 259, 253, 25, 29 gauge13=Boeing747-400!Autopilot Localizer Switch, 256, 90, 29, 29 //is BC button - moved to VS spot, (BC button spot was orig: 256, 64, 29, 30) //gauge13=Boeing747-400!Autopilot Localizer Switch, 256, 64, 29, 30 //orig line for BC button gauge14=Boeing747-400!Autopilot Approach Switch, 226, 96, 29, 29 //gauge15=Boeing747-400!Autopilot VS Switch,256, 96, 29, 29 //switched off, use Altitude-hold instead, location is now BC button. gauge16=Boeing747-400!Autopilot Nav Switch, 226, 126, 29, 29 gauge17=Boeing747-400!Autopilot IAS-Mach Switch, 256, 126, 29, 30 gauge18=Boeing747-400!Autopilot Speed Switch, 257, 285, 29, 29 gauge19=Boeing747-400!Autopilot Altitude Hold Switch, 226, 64, 29, 30 gauge20=Boeing747-400!Autopilot Master Switch, 259, 67, 25, 24 //(BC) 260, 96, 29, 29 //(VS) //orig is: 259, 227, 25, 24 //gauge20=Boeing747-400!Autopilot Master Switch, 259, 227, 25, 24 //Orig AP master spot. - There this button does not show up!

error in this, one sec!

Oh, I also have I way to get at least a few more buttons working in the VC 3d cocpit of the default 747_400. Like the autopilot-on button for example. I'll try to post it soon, but I don't have much time right now and I would need to test it before I post. So it won't be today. I'm not sure if you realise, so just to be sure: The updated cocpit mrzippy provides replaces the cockpit that is now in the 747. So after you install it you can not choose between the default cockpit and the updated one when you choose a plane. Only the updated one will be available. In all textures of the 747_400. il88pp.

The cockpit update that mrzippy linked is very nice. But, you may not like it, or you may get fed up with it after a while. It comes as an auto-installer, and uninstall is sometimes not completely succesful. So, be on the safe side and make a backup copy of your complete b747_400 folder before you install this file. And store it safely. It may come in very handy someday. (Because you can't just get the default planes off the cd later without completely reinstalling or doing a repair install of FSX. And those options both cause lots of problems.) Actually, If you have the disk space, make a copy of the complete "Microsoft Flight Simulator X" folder and store it. Can be on a external harddisk if you want. That way you always have a copy of every default file, just in case you ever delete a file by mistake. Making that backup copy was the first thing I did after I installed FSX a year and a half ago. Happy flights, il88pp.