Re: [Flightgear-devel] The next FlightGear release (summer 2012)

2012-06-08 Thread Renk Thorsten
1) What's the version number of the new release? a) 2.8.0 b) 3.0.0 My impression is that it would be best to advertize Rembrandt as a new, exciting, but optional and stil experimental development. The reason is similar to what others have said - it seems to do really impressive things

Re: [Flightgear-devel] Hawaii regional textures merge request

2012-06-08 Thread Renk Thorsten
Okay, I didn't get a message that this was merged, and despite the argument that there's need for a discussion of the regional texturing scheme there wasn't any discussion, so can I assume the subject isn't interesting at the moment, discontinue to try to come up with GPL compatible solutions

Re: [Flightgear-devel] Hawaii regional textures merge request

2012-06-08 Thread ys
Hi Thorsten Right, it doesn't look like it is worth to have a discussion about this and it was only me pointing this out. At the end I prefer to have your nice work in the repo and it's really not up to me to block anything. I'm just interested in this discussion and I remembered a lot of post

Re: [Flightgear-devel] The next FlightGear release (summer 2012)

2012-06-08 Thread Stuart Buchanan
On Fri, Jun 8, 2012 at 8:35 AM, Renk Thorsten wrote: Personally, I'm not using it since it makes my system just a bit too slow to enjoy and I can't really see how to port lightfield development to Rembrandt (I guess we're not quite there yet as far as infrastructure is concerned, and I'd

Re: [Flightgear-devel] Hawaii regional textures merge request

2012-06-08 Thread Stuart Buchanan
On Fri, Jun 8, 2012 at 8:49 AM, Renk Thorstenwrote: Okay, I didn't get a message that this was merged, and despite the argument that there's need for a discussion of the regional texturing scheme there wasn't any discussion, so can I assume the subject isn't interesting at the moment,

[Flightgear-devel] Two issues: Shader control and turbulence

2012-06-08 Thread Renk Thorsten
Issue #1: We finally found the reason why Heiko didn't get the lightfield scheme properly: /sim/rendering/shader-effects is required to be true in skydome.eff but apparently not set any more by recent GIT, it was however leftover in my autosave, so I didn't notice anything. I can simply

Re: [Flightgear-devel] The next FlightGear release (summer 2012)

2012-06-08 Thread Geoff McLane
Hi, FWIIW I would opt for version 2.8 Concerning Rembrandt, it does not work on either of my 2 ATI cards - Radeon HD 2600 XT, running Ubuntu 64-bit, and Windows Vista 32-bit, and a Radeon HD 7700 series, in Windows 7 64-bit. I think I have tried all the options mentioned here... On the 2600

Re: [Flightgear-devel] Two issues: Shader control and turbulence

2012-06-08 Thread Emilian Huminiuc
On Friday 08 June 2012 09:53:58 Renk Thorsten wrote: tie to some yet unknown master switch? Who has a plan? * Thorsten There's no master switch anymore. There's a property that's checked by some nasal to set the quality of the shaders, but there's no master switch available for effects.

Re: [Flightgear-devel] Two issues: Shader control and turbulence

2012-06-08 Thread Renk Thorsten
The /sim/rendering/shader-effects property has been removed since before 2.6.0, and IIRC it was properly announced on this list. I believe each of those properties was documented on the wiki by Fred, and the major changes were announced on this list. I don't mean to blame anyone for lack of

Re: [Flightgear-devel] Windows crash

2012-06-08 Thread Alan Teeder
From: Alan Teeder Sent: Tuesday, June 05, 2012 5:28 PM To: Flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Windows crash With the latest git FG is crashing whilst the splash screen is shown. I have tried with several aircraft including C172p If I revert the following all

Re: [Flightgear-devel] Windows crash

2012-06-08 Thread Frederic Bouvier
Does Jenkins build exhibit that problem ? Regards, -Fred - Mail original - De: Alan Teeder ajtee...@v-twin.org.uk À: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Envoyé: Vendredi 8 Juin 2012 17:51:18 Objet: Re: [Flightgear-devel] Windows crash From:

Re: [Flightgear-devel] Windows crash

2012-06-08 Thread Alan Teeder
Fred The Jenkins build runs fine, have tested with several aircraft. I am still using VS2008, with fgfs-win32-VS90-3rdParty+OSG-20110911.zip from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/old/. I have tried a complete clean cmake and compile with the same results. Reverting the JSBsim

Re: [Flightgear-devel] Windows crash

2012-06-08 Thread Frederic Bouvier
I had a startup crash on jsbsim just after the update. A clean solved the problem -Fred - Mail original - De: Alan Teeder ajtee...@v-twin.org.uk À: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Envoyé: Vendredi 8 Juin 2012 19:06:50 Objet: Re:

Re: [Flightgear-devel] The next FlightGear release (summer 2012)

2012-06-08 Thread Torsten Dreyer
Thanks for all the replies, summing all up, I end up with the following: The summer release will become v2.8.0. Rembrandt is included but disabled by default and announced as an experimental but cool new feature. We keep the current selection of base package aircraft for 2.8.0. We keep last

Re: [Flightgear-devel] The next FlightGear release (summer 2012)

2012-06-08 Thread Alexis Bory
Le 08/06/2012 20:39, Torsten Dreyer a écrit : Thanks for all the replies, summing all up, I end up with the following: The summer release will become v2.8.0. Rembrandt is included but disabled by default and announced as an experimental but cool new feature. We keep the current selection

Re: [Flightgear-devel] FlightGear developers discussions flightgear-devel@lists.sourceforge.net

2012-06-08 Thread Vivian Meazza
Thorsten -Original Message- From: Renk Thorsten [mailto:thorsten.i.r...@jyu.fi] Sent: 26 May 2012 18:21 To: FlightGear developers discussions Subject: [Flightgear-devel] FlightGear developers discussions flightgear- de...@lists.sourceforge.net Done. Could do with some more

Re: [Flightgear-devel] The next FlightGear release (summer 2012)

2012-06-08 Thread Curtis Olson
All sounds good from here, thanks for pulling lead on this Torsten! On Fri, Jun 8, 2012 at 2:23 PM, Alexis Bory alexis.b...@gmail.com wrote: Le 08/06/2012 20:39, Torsten Dreyer a écrit : Thanks for all the replies, summing all up, I end up with the following: The summer release will

[Flightgear-devel] [PATCH] simgear: update .gitignore to include all current build results

2012-06-08 Thread Chris Forbes
simgear build off /next was leaving a bunch of untracked and unignored files lying around. most of these are new binaries, but some are intermediate files generated during the build. updates .gitignore to ignore all of them. --- .gitignore | 16 1 file changed, 16

[Flightgear-devel] [PATCH] fg: update gitignore

2012-06-08 Thread Chris Forbes
Update .gitignore to ignore another build result --- .gitignore |1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 8a18462..d8d0fd4 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,4 @@ CTestTestfile.cmake .kdev4 *.kdev4 *.pyc

[Flightgear-devel] [PATCH V2] fg: update gitignore

2012-06-08 Thread Chris Forbes
Update .gitignore to ignore another build result V2: Ignore the install_manifest too. --- .gitignore |2 ++ 1 file changed, 2 insertions(+) diff --git a/.gitignore b/.gitignore index 8a18462..1524d4c 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,5 @@ CTestTestfile.cmake .kdev4