General Category > General Discussion

Sceneries do not load after update **SOLVED**

<< < (2/3) > >>

kikigey89:
Because it clearly states it is compatible - So the purchase was based on wrong statement on their website.

virtuali:

--- Quote from: kikigey89 on June 04, 2017, 11:00:14 pm ---Ok but then I want my money back for KCLT as I cannot use it. It clearly states on the KCLT product page: "or Lockheed Martin Prepar3D 1.4 or later, including V4" which is then not true.
--- End quote ---

The scenery is obviously compatible. Our installer relied on the official information in the SDK, which states this system should work from P3D3.0 and up.

Our installer use it from 3.2 and up only, because that's the first version where we could ask P3D to configure a product for us, without messing with config files directly.

But, of course, like all software, bugs exists so, quoting from the P3D 3.4 "What's new":


--- Quote ---Fixed bug that prevented airport scenery added using an add-on.xml from correctly loading
--- End quote ---

Is there a special reason why you don't want to update to the 3.4 ? We can of course update the installer, and have them use the old system of the scenery.cfg unless you are on 3.4 but again, why you still want to use an outdated version of the sim, when you can just download and install the Client.

And no, before you say "because I would have to reinstall all my add-ons", that's NOT the case. Updating from 3.3 to 3.4 requires only this:

- Uninstall the Prepar3d CLIENT  (ONLY the Client)

- Download the latest 3.4 Client only and install it.

Done, 5 minutes, no need to reinstall ANY add-ons.

kikigey89:
Hi Umberto,

I'm also commercial software developer and just a tip from my side: If you know that there's a problem with one version, don't blame LM for that but at least prevent the installer to do anything.
It is clearly not compatible as your software changed the entire folder structure (which I generally like and support) and if you know this bug, then you can't blame LM for it and force the customers to update. Clearly say, there's an issue with 3.3, I can't change anything here, please update to 3.4 but don't say it's compatible.


--- Quote ---And no, before you say "because I would have to reinstall all my add-ons", that's NOT the case. Updating from 3.3 to 3.4 requires only this:
--- End quote ---
Because the last time I did this it crashed my entire P3D install because probably another addon product did something LM didn't think of (and wasn't supposed to do). This time it seemed to have worked (at least it says 3.4 and my default airport loads correctly. Luckily I have several backups...

I'll keep you posted but I hope I can finally enjoy KCLT in the afternoon  ;D

Chris

virtuali:

--- Quote from: kikigey89 on June 05, 2017, 09:02:09 am ---It is clearly not compatible as your software changed the entire folder structure (which I generally like and support) and if you know this bug, then you can't blame LM for it and force the customers to update. Clearly say, there's an issue with 3.3, I can't change anything here, please update to 3.4 but don't say it's compatible.
--- End quote ---

It's LM themseleves which said this was a bug that's was FIXED in 3.4 so, it's really out of the question that was it.

And of course, as soon the bug was found (how could we possibly test on each and every P3D minor version ?), because I found it during a Teamviewer session with an user, ALL our installers have been updated so, the current version which is online now, will still use the scenery.cfg if P3D is not at least 3.4.


--- Quote ---it says 3.4 and my default airport loads correctly
--- End quote ---

Of course it did.

kikigey89:
That's great, because I had some crashes, e.g. it crashes when I select a view group and even when I want to close P3D it crashes in the end.
Will restore the backup now. I don't need a sim which is up to date but just a sim that works with my tools and sceneries ;-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page