January 22, 201610 yr Hi Folks, Anyone tried this one yet? Looks good. http://www.sim-planet.com/en/fsx-downloads/vector-design-move-it-to-p3d.html?utm_source=Simplanet+Newsletter&utm_campaign=35786f6730-SimPlanet+Newsletter+January+2016+%233&utm_medium=email&utm_term=0_c8ddd4ec5e-35786f6730-184588433&mc_cid=35786f6730&mc_eid=1c6779e49b Regards, Jerry Friz “The Wright Brothers created the single greatest cultural force since the invention of writing. The airplane became the first World Wide Web, bringing people, languages, ideas, and values together.” – Bill Gates
January 22, 201610 yr Commercial Member I think migration tool is probably the way to go. Not sure about this Alex Ridge Join Fswakevortex here! YOUTUBE and FACEBOOK
January 22, 201610 yr I think migration tool is probably the way to go. Not sure about this In my opinion, the migration tool is a virus. It corrupts your registry and does not undo the damage if you remove it. The utility posted by Jerry might be useful. However, I've yet to find an airport scenery that I could not install in P3D yet. Sometimes you might have to put a zero size fsx.exe file in the P3D directory but there is always a way to get it done. Also there are some older freeware sceneries that you might have to touch up with ADEX to ensure taxiways don't disappear, I wonder if that utility does that for you. Dan Downs KCRP
January 23, 201610 yr Commercial Member Jerry- I wish I could invoice the makers of some of these migration tools for the amount of product support time PMDG has to provide in order to un-********** customer simulators after the use of these things. As of this moment, we estimate that 40% of the support we provide to customers is related to problems caused by migration tools. Considering that we have 3 full time techs- the impact that has on costs and wait-times is rather staggering. The whole principal behind migration tools is to allow users to port software from one platform to another for which the software may/may not even be compatible. There is little to no thought given to what the effects might be once the customer accomplishes that task- and even less thought given to the impact it has on the customer. Of course- when things don't go as planned, legitimate developers (term used intentionally) wind up having to provide support to our own products that magically stop working and it often takes hours and hours of direct support work before we discover that the problem is the migration tool the customer has installed. I strongly discourage their use. I would hate to get to the point where we have to cut a customer loose from support until they reinstall FSX and P3D migration-tool-free... but we are rapidly heading in that direction. Robert S. Randazzo PLEASE NOTE THAT PMDG HAS DEPARTED AVSIM You can find us at: http://forum.pmdg.com
January 23, 201610 yr Hi Folks, Anyone tried this one yet? Looks good. http://www.sim-planet.com/en/fsx-downloads/vector-design-move-it-to-p3d.html?utm_source=Simplanet+Newsletter&utm_campaign=35786f6730-SimPlanet+Newsletter+January+2016+%233&utm_medium=email&utm_term=0_c8ddd4ec5e-35786f6730-184588433&mc_cid=35786f6730&mc_eid=1c6779e49b Regards, Jerry Friz Bought it but not tried it as yet........................................................ ...........................................................and reading both Dan's and Robert's post, might have been a bad buy in the simMarket Xmas Sale. Rick Almeida
January 23, 201610 yr Jerry- I wish I could invoice the makers of some of these migration tools for the amount of product support time PMDG has to provide in order to un-********** customer simulators after the use of these things. As of this moment, we estimate that 40% of the support we provide to customers is related to problems caused by migration tools. Considering that we have 3 full time techs- the impact that has on costs and wait-times is rather staggering. The whole principal behind migration tools is to allow users to port software from one platform to another for which the software may/may not even be compatible. There is little to no thought given to what the effects might be once the customer accomplishes that task- and even less thought given to the impact it has on the customer. Of course- when things don't go as planned, legitimate developers (term used intentionally) wind up having to provide support to our own products that magically stop working and it often takes hours and hours of direct support work before we discover that the problem is the migration tool the customer has installed. I strongly discourage their use. I would hate to get to the point where we have to cut a customer loose from support until they reinstall FSX and P3D migration-tool-free... but we are rapidly heading in that direction. I agree with this wholeheartedly. It does more harm than good. David Graham Google, Network+, Cisco CSE, Cisco Unity Support Specialist, A+, CCNA
January 23, 201610 yr @Robert The easiest way to Uninstall a product installed with the migration tool is to enable the migration tool then run the Uninstaller. It's worked for me everytime. I use the migration tool in situations where th developer is ok with it IE they allow you to use the same license fo p3d or FSX ie orbx ect. It works great but I expect no support from the devs till an official version is released,if I have issues it up to me to fix them. ATP MEL,CFI,CFII,MEI. Type Ratings B-737, ERJ-190,ERJ-170
January 23, 201610 yr Author Hi Robert, Thanks for your quick reply... I used the migration tool for Aerosofts Anc., and Fairbanks. Figured they would never bring out the P3Dv3.1 version. Both are working fine. I knew it was at my risk. I would not try PMDG, or, any Orbx products,, although I am getting impatient with Orbx..[Waiting].. I would like to install Juneau , and Ketchikan, these are airports that I flew into ,, when I was active on the line. Thanks again Robert. Regards, Jerry Friz “The Wright Brothers created the single greatest cultural force since the invention of writing. The airplane became the first World Wide Web, bringing people, languages, ideas, and values together.” – Bill Gates
January 23, 201610 yr Hi Robert, Thanks for your quick reply... I used the migration tool for Aerosofts Anc., and Fairbanks. Figured they would never bring out the P3Dv3.1 version. Both are working fine. I knew it was at my risk. I would not try PMDG, or, any Orbx products,, although I am getting impatient with Orbx..[Waiting].. I would like to install Juneau , and Ketchikan, these are airports that I flew into ,, when I was active on the line. Thanks again Robert. Regards, Jerry Friz Just an FYI orbx will work fine in p3dv2 or v3 with the migration tool. I have them all working ATP MEL,CFI,CFII,MEI. Type Ratings B-737, ERJ-190,ERJ-170
January 23, 201610 yr I strongly discourage their use. I agree 100% with this ... not to mention the bad reputation it gives LM's P3D when people complain about VAS, CTDs, stutters, and other performance related issues. The sad reality is that legitimate issues and real bugs are sidelined because of the time spent on non-compatible FSX products -- this just hurts everyone especially when those using EMT don't admit to it. My personal take is if one wants to move FSX products over to P3D, then do it manually and be ready to undo it if you run into any issues ... but definitely do NOT request any sort of help/support from the vendor as that just ties up vendor resources that could be put to better use (like a 747 for example). AVSIM mods/staff have debated this frequently, but we're not lawyers/judges soooo ... EMT being a "payware" product definitely doesn't sit well with me, but this is just my OWN PERSONAL opinion and not representative of anything more than that. Cheers, Rob.
January 23, 201610 yr I agree 100% with this ... not to mention the bad reputation it gives LM's P3D when people complain about VAS, CTDs, stutters, and other performance related issues. The sad reality is that legitimate issues and real bugs are sidelined because of the time spent on non-compatible FSX products -- this just hurts everyone especially when those using EMT don't admit to it. My personal take is if one wants to move FSX products over to P3D, then do it manually and be ready to undo it if you run into any issues ... but definitely do NOT request any sort of help/support from the vendor as that just ties up vendor resources that could be put to better use (like a 747 for example). AVSIM mods/staff have debated this frequently, but we're not lawyers/judges soooo ... EMT being a "payware" product definitely doesn't sit well with me, but this is just my OWN PERSONAL opinion and not representative of anything more than that. Cheers, Rob. Rob so many addons work fine in p3dv3 with the migration tool Real Air Duke V2,orbx stuff,Carenado planes,most scenery ect. Its never caused me issues. I don't think there is anything wrong with shoe horning an addon in what I don't get is why people think the devs owe the custom support on an unsupported sim. It's not just migration tool installs causing VAS and performance issues those happen even in fully supported addons due to 2006 era code and 32 bit sim with poor optimization by some addon devs ATP MEL,CFI,CFII,MEI. Type Ratings B-737, ERJ-190,ERJ-170
January 23, 201610 yr Commercial Member What?...Just make sure your tech support ask the customer if he/she is using the Migration tool addon with your product. If they are, don't give them support, simple as that. .What's the big deal? Now you want more $$$ from the MT dev's? Isn't charging for your product twice enough for you guys....SMH! Most devs are bigger than that, and would not want to cold shoulder any customer, whatever the cause of the problems, because it's bad form. To be fair, unless you're developing for both platforms (FSX and P3D) with deeply entrenched code, most stuff you will find works out of the box with FSX and with P3D simply because file format and folder paths are similar. But these sims have forked, and they are now very much diverging technologies. Other devs will have to make the decision sooner or later to fork their own development into two mainstream paths to cover FSX and P3D. Inevitably, these devs will be charging for both platforms too, as they become dissimilar enough. Steve Waite: Engineer at codelegend.com
January 23, 201610 yr I agree 100% with this ... not to mention the bad reputation it gives LM's P3D when people complain about VAS, CTDs, stutters, and other performance related issues. The sad reality is that legitimate issues and real bugs are sidelined because of the time spent on non-compatible FSX products -- this just hurts everyone especially when those using EMT don't admit to it. My personal take is if one wants to move FSX products over to P3D, then do it manually and be ready to undo it if you run into any issues ... but definitely do NOT request any sort of help/support from the vendor as that just ties up vendor resources that could be put to better use (like a 747 for example). AVSIM mods/staff have debated this frequently, but we're not lawyers/judges soooo ... EMT being a "payware" product definitely doesn't sit well with me, but this is just my OWN PERSONAL opinion and not representative of anything more than that. Cheers, Rob. +1 Never used any, never will. If I needed help from PMDG the first thing I would say is " Ive never use......" But "strangely" Ive never needed there help. David Murden. MSFS • Fenix A320 • PMDG 737 • MG Honda Jet • 414 / TDS 750Xi • FS-ATC Chatter • FlyingIron Spitfire & ME109G • MG Honda Jet • • Fenix A320 Walkthrough PDF • Flightsim.to • DCS • A10c II • F-16c • F/A-18c • F-14 • (Others in hanger) • Supercarrier • Terrains = • Nevada NTTR • Persian Gulf • Syria • Marianas • • [email protected] All Cores HT ON • 32GB DDR4 3200MHz • RTX 3080 • TM Warthog HOTAS • TM TPR • Corsair Virtuoso XT with Dolby Atmos® • Samsung G7 32" 1440p 240Hz • TrackIR 5 & ProClip •
Create an account or sign in to comment