Author Topic: Installing KLAX directly into P3D  (Read 7345 times)

Dimon

  • Sr. Member
  • ****
  • Posts: 493
Installing KLAX directly into P3D
« on: September 23, 2014, 06:53:20 pm »
Hi, it's been a long time.

Fresh P3D install, downloaded KLAX installer, ran it (P3D was found) then went into KLAX and only the jetways and ground textures are being visible. No buildings at all.

Also, there is no Virtualli activation module here.

Any suggestions would be much appreciated
i7-6700k@4.6Ghz, Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.

Dimon

  • Sr. Member
  • ****
  • Posts: 493
Re: Installing KLAX directly into P3D
« Reply #1 on: September 24, 2014, 01:25:25 am »
Ok. Reinstalled and installed again. The scenery folders and the addon manager are located in appropriate folders, but P3D cannot see the module and probably this is the reason why I cannot activate the scenery. Any help with activating the addon manager module in P3D would be much appreciated.

Actually, some FAQ with installing the sceneries into P3D would be helpful as well.

Thanks
i7-6700k@4.6Ghz, Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.

Dave_YVR

  • Beta tester
  • Hero Member
  • *****
  • Posts: 802
Re: Installing KLAX directly into P3D
« Reply #2 on: September 24, 2014, 08:14:28 am »
 Interesting, I thought the installer did it all. I never had to do anything with my FSDT airports in p3d. You are of course using the most current installer?

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: Installing KLAX directly into P3D
« Reply #3 on: September 24, 2014, 10:21:24 am »
The FSDT installer is obviously entirely automatic and it works, and there's nothing special to do, other than selecting the option to install into P3D. The only think to take care is, if you use the P3D Migration Tool, it must be disabled when installing and using anything from FSDT or anything else that recognizes P3D natively.

If you don't see the modules, this is a result of a partial/incomplete P3D installation, that somehow hasn't installed the backward compatible Simconnect clients, as discussed here:

http://www.fsdreamteam.com/forum/index.php/topic,10084.msg79077.html#msg79077

Dimon

  • Sr. Member
  • ****
  • Posts: 493
Re: Installing KLAX directly into P3D
« Reply #4 on: September 24, 2014, 04:19:43 pm »
Thanks Umberto,

Actually, I don't use the MT as I'm moving straight from FS2004 to P3D leaving FSX aside. I will try your suggestion later tonight and let you know.

Thanks again.
i7-6700k@4.6Ghz, Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.

Dimon

  • Sr. Member
  • ****
  • Posts: 493
Re: Installing KLAX directly into P3D
« Reply #5 on: September 25, 2014, 01:10:50 am »
The trick did work. Thanks for the suggestion. Impressed with the fact that my FS2004 activation was automatically transferred to P3D
i7-6700k@4.6Ghz, Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: Installing KLAX directly into P3D
« Reply #6 on: September 25, 2014, 10:47:15 am »
The trick did work. Thanks for the suggestion. Impressed with the fact that my FS2004 activation was automatically transferred to P3D

That's because the activation doesn't have anything to do with the simulator, it's stored in your Window registry and is tied to your hardware so, as long as you don't reformat Windows or change hardware, you don't have to reactivate.

Dimon

  • Sr. Member
  • ****
  • Posts: 493
Re: Installing KLAX directly into P3D
« Reply #7 on: September 25, 2014, 03:24:44 pm »
Quick question - is overclocking or changing BIOS settings considered as "change of hardware"?
i7-6700k@4.6Ghz, Z170 Delux, 980Ti-6GB5700, 2TB EVO850, 16GB DDR4 RAM Win7/64 PRO.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: Installing KLAX directly into P3D
« Reply #8 on: September 25, 2014, 05:16:13 pm »
Quick question - is overclocking or changing BIOS settings considered as "change of hardware"?

Overclocking usually isn't. Flashing the BIOS MIGHT, but it really depends on the mainboard and the BIOS release. But really, we don't have the slightest idea about how hardware detection works, it's done internally by Esellerate, and it's just a black box for us.

In any case, if you have used all the products under FS9 until today, changing the sim doesn't make any difference to the hardware detection.