On 18 Nov 2011, at 07:12, ThorstenB wrote:
> I don't know where exactly the BTG loading code starts. But at least the
> function generating the mentioned "We detected an error" message
> (SGBinObject::read_bin) doesn't have a version check. It does read the
> version and then makes version-dep
On 18.11.2011 07:50, James Turner wrote:
> Except, my expectation when adding the new version was, since the
> version check exists in older FG versions, we'd get a better error
> message, eg 'incompatible BTG version' or similar - from the code, I
> would not expect to see the 'We detected an erro
On 17 Nov 2011, at 21:44, ThorstenB wrote:
> Oh yes! Latest TerraGear + FG were fixed, so they no longer cause weird
> display issues with highly detailed scenery. When you use the latest TG
> to generate scenery, which is so detailed so that it needs the new
> feature, then you also need late
Am 17.11.2011 21:54, schrieb J. Holden:
> Thanks for your response.
>
> The TerraGear build finished successfully, could this be a problem
> with a stable 2.4 build not liking a new TerraGear scenery format,
> especially with detailed scenery?
Oh yes! Latest TerraGear + FG were fixed, so they no l
Thanks for your response.
The TerraGear build finished successfully, could this be a problem with a
stable 2.4 build not liking a new TerraGear scenery format, especially with
detailed scenery?
Cheers
John
--
All the d
Am 17.11.2011 18:55, schrieb J. Holden:
> Apart from not being happy fgfs apparently now reverts to local
> weather on simple command-line startup, the final three lines: "We
> detected an error while reading the file" are incredibly
> undescriptive - what file is being read? I assume this has some
Hi everyone,
Just compiled three degrees of improved scenery in southwest Colorado
(including airports KDRO, KTEX). My problem is FlightGear hangs upon loading
the scenery. It's still responsive because the refresh-meter keeps working in
the bottom left, but the scenery never loads.
This is my
7 matches
Mail list logo
