Hi Guys,
A 30 second thought on this:
On Tue, Jun 25, 2013 at 10:58 PM, Curtis Olson wrote:
> Once we clear past the 2.10, 2.12, etc. series, I'd like to go back to
> keeping things single digits in the major and minor version numbers and when
> we run out of a single digits bump up the major nu
Am 26.06.2013 09:58, schrieb James Turner:
Yep, works for me too.
James
Thanks, Stuart for finding a solution.
I have just pushed the version number 2.12.0 to SG, FG and FGDATA.
Torsten
--
This SF.net email is spon
On 25 Jun 2013, at 22:48, Stuart Buchanan wrote:
> Declaring that the Feb 2014 release will be 3.0 now will give everyone plenty
> of
> notice, and might encourage efforts to fix bugs in the next 6 months. I'm
> aware
> that my FG development time is more limited these days, and given activit
>> Having thought about this a bit more I'm going to propose we do 2.12.0
>> now and
>> "pre-announce" 3.0 as the Feb 2014 release to give us just a little
>> more time
>> to prepare and make the 3.0 as polished as possible. After all, it'll
>> be the third
>> major release in 15 years :) .
O
On 26 Jun 2013, at 08:42, Vivian Meazza wrote:
> Makes sense to me,
Yep, works for me too.
James
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
> From: Anders Gidenstam [mailto:anders-...@gidenstam.org]
> Sent: 26 June 2013 07:41
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] reminder: entering feature freeze now
>
> On Tue, 25 Jun 2013, Stuart Buchanan wrote:
>
> > Having though
On Tue, 25 Jun 2013, Stuart Buchanan wrote:
> Having thought about this a bit more I'm going to propose we do 2.12.0 now and
> "pre-announce" 3.0 as the Feb 2014 release to give us just a little more time
> to prepare and make the 3.0 as polished as possible. After all, it'll
> be the third
> maj
On Tue, Jun 25, 2013 at 4:48 PM, Stuart Buchanan wrote:
> Having thought about this a bit more I'm going to propose we do 2.12.0 now
> and
> "pre-announce" 3.0 as the Feb 2014 release to give us just a little more
> time
> to prepare and make the 3.0 as polished as possible. After all, it'll
>
On Mon, Jun 24, 2013 at 10:41 PM, Torsten Dreyer wrote:
> Collecting the arguments from this discusson, I can see good points for
> a 3.0.0 release. Most convincing was Stuarts comparison against 2.0.0
> and the progress we made since that version.
>
> My suggestion is, we dare to call the 2013 sum
Hi Stuart,
> Ah yes. I remember you mentioning this before, me saying I'd add it
> to my TODO list, and then failing to do so. Sorry. I've now added it
> to my wiki TODO list so I don't forget again. Are you thinking about
> the sprinkling of lights that we put over the terrain, the VASI/PAPI
Hello,
By the way , does the terrain object bug, has been fixed, can we land on
buildings and any others solid objects.
I for days (may be weeks) i won't have any access to Git , so i won't be
able to check it.
Thank
Ahmad
On 24 June 2013 23:14, James Turner wrote:
>
> On 24 Jun 2013, at
On Thu, Jun 20, 2013 at 11:57 AM, Renk Thorsten wrote:
>> - ALS now works much better with the random trees. I think
>> there's still work to be done with other shaders (presumably
>> the wake shader has still to be ported?)
>
> Yes (if that is really a major holdup, I can probably do this within
> I apologize for missing the point.
No need to apoligize at all.
If anybody is annoying somebody, it's me with my scheduled emails about
release deadlines, my requests for following a specific release
procedure and for raising discussions about version numbers.
Some time ago, we agreed on sett
On 24 Jun 2013, at 07:53, Gijs de Rooy wrote:
> Wherever I mentioned 2.12, it was because that's the logical follow up on
> 2.10. If we didn't decide anything, we'd "automatically" end up with 2.12
> instead of 3.0.
>
> That's all. I wouldn't worry too much about someone who's telling what ot
people think, without he himself taking part in the discussion.
Gijs
> From: thorsten.i.r...@jyu.fi
> To: flightgear-devel@lists.sourceforge.net
> Date: Mon, 24 Jun 2013 06:27:32 +
> Subject: Re: [Flightgear-devel] reminder: entering feature freeze now
>
>
> R
Referring to the version number discussion, I've been given to understand here
http://www.flightgear.org/forums/viewtopic.php?f=19&t=20137#p185619
that there have been already "core developers referring to the next release as
2.12" a while ago who would now be "obviously pretty annoyed about it
> But hey, since you think I don't know anything anyway and just pretend
> to be smart here, why don't you go looking for a different and really
> smart person to code you what you like. Or better yet, do it yourself.
> Because I have enough of this - I'm suspending my offer to help merging
> R
Hello,
The most disappointing , is it seems we are getting better performances
with a lower quality Graphic Card ( talking about Nvidia family ).
This won't encourage to buy a better one.
But more technical explanations , architecture of the computer, operating
system... which could explain,
That
On Thu, Jun 20, 2013 at 9:29 PM, James Turner wrote:
> Emilian has explained on IRC this might be due to the out-of-the-box /
> default config for Rembrandt being highly suboptimal, which I didn't yet
> evaluate, I would be delighted to have it more usable. I'm going to test
> further over the week
> I guess the professional you are has done statistics about the FG users
> world, thus you are able to be more precise about those unfortunate users
> who are getting only "the single frame per second", which hardware? which
> operating systems ?
Strangely enough I have (you might have noticed by
I won't say again the performances i got with a GTX 560TI , since given
within the recent topic Rembrandt performance, with the self explaining
.snapshots.
Whatever we need that Benchmark matrix .
Those performances could be very different since depending on the scenery
parameters, for inst
On 20 Jun 2013, at 17:54, Stefan Seifert wrote:
> With an AMD Radeon HD 5670 using free radeon driver I've never seen
> performance of more than 15fps with Rembrandt and if I turn shadow details up
> so they don't look crappy I get about 3-4fps.
And with a i3770K and a GTX670, I get some hit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On an Intel HD 3000 Integrated Graphics Card with Mesa (note that Intel
is generally worse than Nvidia and AMD), I have roughly the same frame
rates with ALS on and with ALS off; it doesn't seem to make much of a
difference in terms of frame rates.
On Thursday 20 June 2013 17:55:40 grtuxhangar team wrote:
> I guess the professional you are has done statistics about the FG users
> world, thus you are able to be more precise about those unfortunate users
> who are getting only "the single frame per second", which hardware? which
> operating sy
Oh, yes there is also computers which can't run FG 2.00 , i have
inherited a computer with nvidia 6200 AGP which run only FG 1.00.
But you will say i (we) am (are) not representative of the FG users
world only an exception, ... anybody is an exception.
I guess the professional you are ha
> Referring to my poor experience with these two computers , i conclude , i
> can accept a decrease of performance, without loosing any FG facility.
> I'll be far from "the single frame per second" your are talking about.
First of all, there are people who get a single frame per second with Rembra
Hum, Given your answer, you have probably some personal memory leak.
I have to remind you, about Rembrandt: Was said before.
With my Computer NVIDIA GPU Geforce 9600 GT at 1024x800 i never get less
than 24 fps
With an other computer NVIDIA GPU 560 Ti was demonstrated ( refer to
Rembrandt perfo
> - ALS now works much better with the random trees. I think
> there's still work to be done with other shaders (presumably
> the wake shader has still to be ported?)
Yes (if that is really a major holdup, I can probably do this within the next
weeks if it makes Vivian smile :-) ...).
A more
> Pushing in front your supposed to be know how is not an argument ,
> usually the more person' s know how is great the less they are
> pretending to have it.
> Please stop to pretend to be the best.
So you mean to say that actually having written all the ALS code has not in any
way given me
Hey Stuart!
I understand now. I guess that is why by trying to set Rembrandt=ON through the
Internal properties while the sim is running results in distorted rainbow
colors...
Thank you for explaining this to me! Hope you guys find a way around this! :)
Cheers,
Kleo
Sent from my Gentoo
On 1
On Wed, 19 Jun 2013 12:42:33 +0100, Stuart wrote in message
:
> On Tue, Jun 18, 2013 at 11:08 PM, Kleo G. wrote:
> > ALS already has an ON/OFF selection button.
> >
> > Wouldn't it be useful for Rembrandt to also have such a button,
> > thus being able to switch it on or off either without restar
On Wed, Jun 19, 2013 at 7:07 AM, grtuxhangar team wrote:
> Pushing in front your supposed to be know how is not an argument ,
> usually the more person' s know how is great the less they are pretending
> to have it.
> Please stop to pretend to be the best.
> Don't tell the FG feature can't be i
On Tue, Jun 18, 2013 at 7:40 AM, Renk Thorsten wrote:
>> What version number will we give to the new
>> release? Are we ready for a 3.0 or is it 2.12?
>
> Looking through my list of goals for the last coding period:
I also had a look through the 3.0 backlog article
(http://wiki.flightgear.org/Flig
Pushing in front your supposed to be know how is not an argument ,
usually the more person' s know how is great the less they are pretending
to have it.
Please stop to pretend to be the best.
Don't tell the FG feature can't be improved with Rembrandt by exposing
some similar eye candy you are g
On Tue, Jun 18, 2013 at 11:08 PM, Kleo G. wrote:
> ALS already has an ON/OFF selection button.
>
> Wouldn't it be useful for Rembrandt to also have such a button, thus being
> able to switch it on or off either without restarting the sim??
> It would skip all the inconvenience of restarting the sim
gt; From: thorsten.i.r...@jyu.fi
> To: flightgear-devel@lists.sourceforge.net
> Date: Tue, 18 Jun 2013 16:26:16 +
> Subject: Re: [Flightgear-devel] reminder: entering feature freeze now
>
> > 3/ To wait for better development reaching the target to have REMBRANDT
> &
> 3/ To wait for better development reaching the target to have REMBRANDT
> and
> ALS working well all together, and definitively included within FG.
(...)
> The basic content remains the same, some Aircrafts are flying with
> Rembrandt not with ALS , others are flying with ALS not with Rembrandt
What is the most important ?
1/ To have a working stable Program whose the major options ( ALS,
REMBRANDT) remains options since conflicting each other.
2/ To have a working stable Program which include as a standard one of
these two options, which would definitively push on the back the oth
> A nice list and it's all worthwhile improvement, but it's all tinkering
> around the edges of existing stuff. There's no step change which would
> justify 3.0 IMO. For that we need something major, like new terrain
> (850) or Rembrandt as the default.
*shrugs*
This would depend on if you're
On 18 Jun 2013, at 09:38, Vivian Meazza wrote:
> We still
> cannot select the Screenshot Directory from the gui. I think that all argues
> for 2.12.
Hmm, that is 'just a bug' which will be fixed during the release cycle, I just
keep forgetting about it since there's no issue i the tracker and
Thorsten
> Sent: 18 June 2013 07:40
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] reminder: entering feature freeze now
>
> > What version number will we give to the new release? Are we ready for
> > a 3.0 or is it 2.12?
>
> Looking th
> What version number will we give to the new
> release? Are we ready for a 3.0 or is it 2.12?
Looking through my list of goals for the last coding period:
> * Get a high-quality model shader running under Atmospheric Light Scattering
This is now available, working for random buildings and for s
Once the version has been decided, will the branches be created?
Saikrishna Arcot
On Mon 17 Jun 2013 01:59:47 PM CDT, Torsten Dreyer wrote:
> Hi everybody,
>
> for most of us, it's June, 17th which marks the day for the feature
> freeze period, lasting until July, 17th.
>
> Everybody is invited t
Hi everybody,
for most of us, it's June, 17th which marks the day for the feature
freeze period, lasting until July, 17th.
Everybody is invited to walk through the lessons learned section of our
release plan at
http://wiki.flightgear.org/Release_plan
the bugtracker at
http://code.google.com/p/
44 matches
Mail list logo
