Yes, I am attempting to put it into P3D.   Does this mean CS have joined the few companies deliberately blocking installation into the other sim?  Or is there a technical glitch at work.  The previous version installed easily and I shall return to that.  I have never had a problem using the FSXtoP3D migrator, and certainly not with the previous version.  Ah well, Star Wars continues.

macca22au wrote on Jul 13^th, 2013 at 12:43am:
All of them fly beautifully in P3D (well except for 777 v1.2). I am trying to think of something that might fix this in P3D, but I have not tried anything yet. Having trouble getting quite a few addons working in P3D, is the major reason for why FSX is still installed on my computer.

I tried commenting out the update gauge too. I think ACE can do it for you, but I don't think it works for P3D though.
I can't verify this because FSX is installed on my computer as well and so even from Prepar3D\Captain_Sim\777\ace, it changes the 777 FSX (well the Pax/Cargo changes in FSX).

Also, you should change the number on the final gauge:

[Window00]
.....
gauge00=Captain_Sim.x777.sys!main, 0,0, 1,1
gauge01=Captain_Sim.x777.sound!main, 0,0,1,1,Captain_Sim\777\sound.ini
//gauge02=Captain_Sim.x777.update!Main, 0, 0,  3, 3[/b]
gauge02=Captain_Sim.x777.wxr!main,1,1,1,1 <- make this gauge02 to replace the commented out gauge02 update gauge!

It may still work without there being a gauge02, but I haven't checked this.

Well, some I got some good news and some not so good news...

Good news - I got it working in Prepar3D.

Not so good news - Not really sure how I did it, ha!  

Let's see, I did use the comment out line as those done before.  But I messed with the Registry trying to trick the paths as to whether I was installing to FSX or P3D.

I think I:

1. Uninstalled everything (777 that is) on both FSX and P3D.
2. Installed 777 in FSX to make sure everything was working correctly.  It was.
3. Installed version 0.800 on P3D using the Migrator tool.  My plan was originally to compare 0.800 to 1.2 files, filenames and sizes to see if f I could find any differences.
4. I then went to the registry and searched on 'captainsim' to what was in there.  I found a section for the 777 showing the paths for uninstalling and where it was installed.  That was my FSX path.
5. I changed the path(s) to where my P3D is installed and then installed 777 v 1.2 once again.
6. It came up as a "repair" this time and continued with the repair but to P3D.
7. Went back to the registry and changed all paths back to the FSX paths.
8. Rebooted the PC just to be sure.
9. And now it seems to be working.

I think it's working as I noticed there was a difference in the opacity of the engines when running.  You can see through them alot more in v1.2.  The landing gear is there and so all all the gauges and surface controls.

Note the version in ACE showing 1.2.0.0 so I think it's correct but I'm sure experts can verify.  

Sure seems to be real heavy in FPS in the VC.  Like I loose 30%.  May be why I was not really using this anymore.  I was planning to just hide the VC and use my cockpit hardware but it appears my GoFlight EFIS and MCPpro will not match up to it.  Funny, some of my Saitek stuff does, though.

Anywho,  please don't take the above as gospel.  I was just messing around and got lucky I think.  Plus I didn't about install and un-installing several times as I have not really customized  anything in there.

That also reminds me several posts here talk about changing the [AUTOPILOT] section with some new numbers.  I checked my cfg and those numbers were already there?  Oh well...  all in good fun!

This is the end of  the story. I cannot fly 777.1.2.because I need to have 0.8 version to load 1.2 version to complete the loading.


http://img607.imageshack.us/img607/5393/rnrr.jpg
http://img5.imageshack.us/img5/4051/bx8h.jpg

Markoz wrote on Jul 13^th, 2013 at 2:49am:



I used to think that P3D was the answer to a superior simulator to FSX, but I have come to realize that P3D is based on the old code from FSX at it's core. So any new features by the P3D developers that are added to P3D could be restricted by the old code that P3D rests on. As it stands now in my opinion, is that FSX with all its warts, is still a slicker simulator then P3D. I believe that possibly XPlane may have the answer to a superior simulator for flight. Here are the pros for XPlane , it has DirectX 11; 3D scenery structures, latest support for the newest advances in graphics; flight model is much more realistic; airports are depicted in a realistic way as opposed to FSX, and P3d, where the airstrip is an unrealistic flat as a pancake, and perfectly level piece of concrete; XPlane is a 64 bit application, thereby allowing for it's unlimited use of all the memory you can throw at it; and it's ability to fully implement multi-core processors to their fullest extent. On the down side XPlane is very unpolished; not user friendly; no in house structures at any airport in the world, except with only one exception; too many useless aircraft, that have very little value as a simulator enthusiast. I believe FSX is the best way to go at present if you take into consideration it's limitations, and not wasting your money on too many scenery upgrades that cover the world, as well as some of the utilities that are useful, but since some work in the background, they take some of the CPU power away from FSX. DirectX 11 is definitely better then directX 9, but to think that when P3d adds directX 11, that it will significantly improve frame rate is in my opinion wishful thinking. I have all three, and I will probably wait for something much better before I drop FSX. Possibly XPlane.

"changed the Gauge entry as per previous versions"
Will you please inform which Gauge entry did you change?
Can you put copy of the Gauge entry line?
THX

No still I have no landing gear and  all PDF screens are black.
Thanks