On Fri, 08 Jun 2012 12:00:47 +0200, Geoff wrote in message
1339149647.1793.1.camel@DELL02:
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
..the latest (12.04)?
64-bit,
..dmesg |grep -i
On Thu, 7 Jun 2012 18:59:02 -0600, syd wrote in message
cabs5ffn+fn_tt2rbcwxp-pcu5ucd-7fmkavdqpgadbmporb...@mail.gmail.com:
Rembrandt has been around for quite a few months now,
and the changes required to make an aircraft Rembrandt-compatible
are pretty small, even if the changes to add
The summer release will become v2.8.0. Rembrandt is included but
disabled by default and announced as an experimental but cool new
feature.
Rembrandt is not the default renderer and to follow the consensus,
I won't add a Rembrandt option to fgrun. The braves willing to
experiment will have
: [Flightgear-devel] The next FlightGear release (summer 2012)
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Date: Friday, June 8, 2012, 12:00 PM
Hi,
FWIIW I would opt for version 2.8
Concerning Rembrandt, it does not work on either
of my 2 ATI cards - Radeon
On Sun, Jun 10, 2012 at 7:37 AM, Frederic Bouvier wrote:
The summer release will become v2.8.0. Rembrandt is included but
disabled by default and announced as an experimental but cool new
feature.
Rembrandt is not the default renderer and to follow the consensus,
I won't add a Rembrandt
...@yahoo.com
À: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Envoyé: Lundi 11 Juin 2012 10:17:33
Objet: Re: [Flightgear-devel] The next FlightGear release (summer 2012)
I wonder how it was done back in 2002 for Doom3 with OpenGL.
Doom3 looks great, a huge contrast
So why not use that technique for shadows?
Anyway, I await 2.9 for the new 850 format...
--- On Mon, 6/11/12, Frederic Bouvier fredfgf...@free.fr wrote:
From: Frederic Bouvier fredfgf...@free.fr
Subject: Re: [Flightgear-devel] The next FlightGear release (summer 2012)
To: FlightGear
Sounds good , I hope someday to be able to see the results .
My list of aircraft is:
dhc2
dhc6
777 , though there are a number of other commiters now , but dont
think this will affect anything
a6m2
dc6-b
Sikorsky-76C
R22
b1900d
Citation-Bravo
Citation-II
Citation-X
Aerostar-700
P47
I should be
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
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
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
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
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
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
On Sat, Jun 2, 2012 at 8:36 PM, Torsten Dreyer wrote:
Two questions have to be discussed and answered until the release
branches get created on July, 17th:
1) What's the version number of the new release?
a) 2.8.0
b) 3.0.0
Given the introduction of Rembrandt, I'd suggest 3.0.0. It's
a
Personally I'd leave 3.0 for the new apt 850 support. If that's not in for
summer leave it at 2.8.
--- On Thu, 6/7/12, Stuart Buchanan stuar...@gmail.com wrote:
From: Stuart Buchanan stuar...@gmail.com
Subject: Re: [Flightgear-devel] The next FlightGear release (summer 2012
If the new autogen will be included, I'm also in favor for a 3.0.0
version numbering.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and
On Thu, Jun 7, 2012 at 2:17 PM, Michael wrote:
Personally I'd leave 3.0 for the new apt 850 support. If that's not in for
summer leave it at 2.8.
I think we need a new world scenery generation to take place to take
full advantage of apt 850 support. I don't know if that's on the
cards for
Good to know.
I'd dedicate some CPU time to world scenery generation, but I'm not
sure how many months that would take... :S
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's
Hello,
Two questions have to be discussed and answered until the release
branches get created on July, 17th:
1) What's the version number of the new release?
a) 2.8.0
b) 3.0.0
Keep it consistent: 2.8.0
My reasons:
-Rembrandt is still experimental and Fred's To-Do-list is still big. I
As I mentioned some weeks ago I think we should leave path of creating world
scenery in one task. I made a proposal how to create world scenery in chunks
all day and nights with jenkins on different machines for different regions.
The sources for this creation process can remain on one master,
Hi all!
Calling something a major release is not just a matter of what's possible,
but also what's done.
There's a lot possible with Rembrandt, but 99% of our aircraft don't use it.
And lots of aircraft look ugly with Rembrandt
(non-translucent windows and fake shadows mostly). I just
Just to add a note what is already running on this jenkins right now, on
different slaves:
- hgtchop available SRTM-3 data (I make use of the no data filled files I
provide), this a one day job on very old machine
- terrafitting the data (another one day job on the same old machine)
- taking
Le 07/06/2012 18:04, Gijs de Rooy a écrit :
There's a lot possible with Rembrandt, but 99% of our aircraft don't
use it. And lots of aircraft look ugly with Rembrandt
(non-translucent windows and fake shadows mostly). I just checked the
few aircraft that I remember being included in the base
On Thu, Jun 7, 2012 at 5:04 PM, Gijs de Rooy wrote:
Hi all!
Calling something a major release is not just a matter of what's possible,
but also what's done.
There's a lot possible with Rembrandt, but 99% of our aircraft don't use it.
And lots of aircraft look ugly with Rembrandt
Stuart Buchanan wrote:
I'm not sure that is correct, but my memory is dim. My recollection was that
even after we converted the main cvs branch to OSG, we kept a plib branch
that was used for a subsequent release.
There's a key difference: The OSG port, at least when it was added to
CVS, was
On Thu, Jun 7, 2012 at 10:44 PM, Martin Spott wrote:
Stuart Buchanan wrote:
I'm not sure that is correct, but my memory is dim. My recollection was that
even after we converted the main cvs branch to OSG, we kept a plib branch
that was used for a subsequent release.
I was wrong - 1.9.0 was
Stuart Buchanan wrote:
So you would prefer not to mention it in the change log and release
note?
In order to save everybody from pointless discussion, I won't disclose
my preference. Anyhow I'd vote for seriously taking into account,
that, for a large fraction of FlightGear's user base,
Rembrandt has been around for quite a few months now,
and the changes required to make an aircraft Rembrandt-compatible are
pretty small, even if the changes to add proper lights are more involved.
If I was being harsh I'd suggest that the aircraft maintainers should
man up and do it.
Michael
--- On Thu, 6/7/12, ys flightg...@sablonier.ch wrote:
From: ys flightg...@sablonier.ch
Subject: Re: [Flightgear-devel] The next FlightGear release (summer 2012)
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Date: Thursday, June 7, 2012, 7:36 PM
Just
On Saturday, June 02, 2012 22:36:17 Torsten Dreyer wrote:
Hi,
in just a bit more than two weeks from now we reach June, 17th, marking
the first milestone for the release of next FlightGear version: the
feature freeze period.
If you have some great and exciting new features for FlightGear
Two questions have to be discussed and answered until the release
branches get created on July, 17th:
5) Do we consider Rembrandt complete/stable enough to be part of the release?
(answering this question gives you the answer to question 1)
Hi Torsten
What are the plans now for apt.dat.gz and nav.dat.gz ? Will this prehistorical
data files still be shipped with flightgear base package 2.8.0 ? As far as I
understand flightgear is ready to read the newer formats and also the airport
scenery tools are ready to use the newer formats.
On Sat, 02 Jun 2012 21:36:17 +0200, Torsten wrote in message
4fca6b31.3090...@t3r.de:
Hi,
in just a bit more than two weeks from now we reach June, 17th,
marking the first milestone for the release of next FlightGear
version: the feature freeze period.
If you have some great and
34 matches
Mail list logo
