De: Torsten Dreyer
Am 02.03.2012 19:03, schrieb Frederic Bouvier:
Now that release 2.6 is out, perhaps it is time to discuss further
developments concerning project Rembrandt.
Although it may already produce pretty images when used by a
talented designer (see for example the P92), it
Stuart Buchanan wrote:
Given that we have 400+ aircraft that need to be updated, I think we
also need clear documentation (on the wiki?) describing the steps you
outline above, and in particular how to register the transparent
surfaces. That probably needs to be in place before the code goes
Is there any chance to make Rembrandt switchable (on/off) at startup?
That should be doable, but not done for the moment. Changes are located
in CameraGroup.[ch]xx and Renderer.cxx for the flightgear side, in
sgmaterial.lib for the simgear side and in Effects/ and Shaders/ for the
data side,
Hi Fred,
On Friday, March 02, 2012 19:03:13 Frederic Bouvier wrote:
thoughts ?
Since we are now at the beginning of a release cycle, I would think now is the
right time.
For the question to preserve both renderers, compatibility of models I think
that we need to preserve both if we cannot
On Sat, 2012-03-03 at 07:25 -0600, Curtis Olson wrote:
I agree that we should merge the project rembrandt work sooner rather
than later. However, we should also take some time and effort to make
sure Thorsten's sky/haze/horizon effects are accounted for as well. I
don't know what issues
-Original Message-
From: Erik Hofman
Sent: Saturday, March 03, 2012 1:36 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Project Rembrandt - next steps
Personally I would think adding Project Rembrandt will call for
FlightGear version 3.0. So if it is added I
Am 03.03.2012 12:43, schrieb Christian Schmitt:
Stuart Buchanan wrote:
IMO we should bite the bullet and get it into next this week if
possible. There's obviously some risk to our 6 month release
schedules that we'll just have to accept.
I agree here. Let's merge the Rembrandt work
-Original Message-
From: Frederic Bouvier
Sent: Saturday, March 03, 2012 11:33 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Project Rembrandt - next steps
De: Torsten Dreyer
I don´t know if that already been covered, but is it possible to make a
model
On Fri, 2 Mar 2012 20:51:59 +
Stuart Buchanan stuar...@gmail.com wrote:
Given that we have 400+ aircraft that need to be updated,
Looks like an aircraft needs some maintenance over time. This somehow
bothers the question whether it is wise to collect 300+ rudimentary
aircraft with no
2012/2/23 Martin Spott martin.sp...@mgras.net:
Apparently I've been too ambitious and idealistic. I know that
voluntary OpenSource development is primarily ego-driven, but there's a
strong indication that I've still under-estimated the average Scenery-
developers narcism: Scenery development
Am 03.03.2012 12:33, schrieb Frederic Bouvier:
But just curious : how many of you reviewed the current code ?
n+1
Just checked out your project/rembrandt branches. Code compiles fine on
64bit openSUSE 12.1 with OSG from trunk.
Running fgfs spits out many messages, most prominent are:
can't
Salut Bertrand,
thanks for your balanced statement. There's a lot I could explain and
you deserve a proper response, if you like. Anyhow I've been with this
project for long enough to know that I'm not going to change anything,
not matter what I'd be resond (and how). Therefore I'm inclined to
- Mail original -
De: Torsten Dreyer tors...@t3r.de
Am 03.03.2012 12:33, schrieb Frederic Bouvier:
But just curious : how many of you reviewed the current code ?
n+1
Just checked out your project/rembrandt branches. Code compiles fine
on
64bit openSUSE 12.1 with OSG from
Am 03.03.2012 03:28, schrieb Robert:
2012/3/2 ThorstenB bre...@gmail.com mailto:bre...@gmail.com
But we don't know why this only happens with the ATI,
only with their driver versions 11.5 and above, and only on Windows.
Thorsten, this bug is also present on Linux (in my case), and I
De: ThorstenB
Also, the project is quite good in finding issues, once new stuff is
in git. But, generally we are not so good in fixing problems then.
Notoriously, everyone has just too little spare time ;-), so a lot of
issues just starve in the tracker. And with hard-core OSG stuff,
Hi all,
just checking out the lattest code as of 15min ago and found that
genapts is not being built/installed.
I checked my build process and found no errors and the program was
missing
can anyone help?
localhost terragear-cs # make install
[ 3%] Built target poly2tri
[ 10%] Built target
Maybe there is a missing dependency that silently discard genapt from the build
Regards,
-Fred
- Mail original -
De: Jason Cox
À: flightgear-devel@lists.sourceforge.net
Envoyé: Samedi 3 Mars 2012 23:41:41
Objet: [Flightgear-devel] terragear not building and installing genapts
Hi
On Sat, Mar 3, 2012 at 1:36 PM, Erik Hofman wrote:
Personally I would think adding Project Rembrandt will call for
FlightGear version 3.0. So if it is added I would create two branches,
version 3.0 and version 2.7 in which the later is switched to bug fixes
only.
Surely a bug-fix 2.7.0 branch
Le 03/03/2012 23:12, ThorstenB a écrit :
Am 03.03.2012 03:28, schrieb Robert:
2012/3/2 ThorstenBbre...@gmail.commailto:bre...@gmail.com
But we don't know why this only happens with the ATI,
only with their driver versions 11.5 and above, and only on Windows.
Thorsten, this bug is
Fred,
I found the issue. it was a missing install of newmat.
cmake didnt indicate that this was going to be a problem when I went to
build and so i ignored it.
I think that this needs to actually stop the build from proceeding as it
stops any worth while build from going on ( not much point in
On Fri, 2012-03-02 at 12:39 -0600, Curtis Olson wrote:
Hi Ian,
If you wish to set your own tower position, it's pretty straight
forward and can be done manually or via nasal or probably a few other
mechanisms.
By default flightgear will set the tower position to the nearest
airfield,
21 matches
Mail list logo
