"Base package check failed"

[Bravo]

Sweet, thanks!
I'll tell you if it works.

UPDATE: Works like a charm! Thanks again.

Also, a quick question. When getting the fgdata, do I get the newest version of every single plane?

[Gijs]

You get the latest version of the aircraft in Git yeah, the ones that will show up on the official download page. Anything else needs to be downloaded elsewhere...

[TrueNorthist]

I downloaded and installed the binary and updated the data directory and FG is running like a champ. Near KNUQ during my test ride I thought I saw a shower off about 3 miles away and what do you know. It was. This sim just continues to amaze me. Landings are very realistic with the advanced weather enabled. Bloody marvelous.

Thanks for the help Gijs.

[Hooray]

fg/sg next and fgdata master, all have 2.12 correctly set. For fg/sg running cmake and afterwards compiling and installing should normally be enough...

Okay, I think I have finally found out what's causing this and why so many people seem to be affected by it every once in a while: $SG/$FG_SRC/version is used by CMakeLists.txt, but touching/modifying it (git pull), does NOT result in a re-configuration - instead, the old contents are re-used from cmake cache.

To see for yourself: Go into your source tree, edit the version file - and switch back to your build tree: no reconfiguration taking place ... thus, you'll get a next/binary looking for 2.11 instead of 2.12, even though 2.12 is the string in all three version files

[TheTom]

We will probably just need to add the version files as dependencies for all build targets inside te CMake config files.

[Hooray]

yes, that should work - sort of like a header: ../../version
the less hackish alternative would be using add_custom_target() which supports a DEPENDS directive:

[Hooray]

I only just realized after pulling next/2.99 that this is still an issue for people using a pre-existing build environment without manually reconfiguring via cmake first.

[TrueNorthist]

The problem has returned. I just tried to install the latest build and am getting the same error again. I have checked the version for fgdata and it is 2.99.0 but the launcher nevertheless gives me the "base package check failed" message. Is this because I have not manually reconfigured via cmake, as Hooray states above? How does one reconfigure via cmake so this error does not reappear?

[Hooray]

http://wiki.flightgear.org/Scripted_Com ... n_Pitfalls

[TrueNorthist]

Forgive me, but I have never run cmake before. I don't even know where it is. Is it something that runs in Git Bash? Regardless I will create a new directory tree in another location and see if that fixes things.

[TrueNorthist]

The completely new tree didn't help. this is exactly what I am getting when I try to launch:

Base package check failed:
Version [none] found at: D:\FlightGear4\bin\win64\data
Version 2.99.0 is required.
Please upgrade/downgrade base package... etc

It does not appear to even see fgdata at all. If I look at the version file in fgdata it says it is version 2.99.0.

Again, I have no idea how to clear the cmake cache... Any assistance would be greatly appreciated.

[Gijs]

Are you sure FG_ROOT is set correctly? D:\FlightGear4\bin\win64\data looks a bit suspicious. Would expect it to be like D:\FlightGear4\data ... Double-check the version file is indeed in the given directory.

[TrueNorthist]

Thanks Gijs. You were bang-on correct. I made an incredibly stupid mistake. After updating I typically create a new shortcut on my desktop for launching FGrun, but for some reason, this time I had created a shortcut of fgfs.exe instead of fgrun.exe. I'm sorry to have wasted your time fellas. It was simple incompetence on my part... But thanks all the same.