The downside is that I think it would require adding
an if()
test to the vertex shader, something I've been avoiding due to
(unfounded?)
concerns about performance.
General advice that I can find is that GLSL is designed as a linear
program:
conditionals and loops are best avoided:
Hi Toshi,
According Fred's comment in
http://code.google.com/p/flightgear-bugs/issues/detail?id=1027#c9
those messages are output by fgrun reading the file:
$fgdata/Aircraft/C130/kc130-yasim-cnf.xml
thanks for the pointer! This is now fixed in fgdata.
Cheers,
Gijs
On Fri, May 3, 2013 at 6:15 PM, Vivian Meazza wrote:
I re-installed the Jenkins nightly Win build from yesterday – seems OK,
although I have NOT done any extensive testing. I’m seeing regular crashes
here from ALS and Rembrandt, but that’s nothing new. I’m getting a number
of errors on
,
Gijs
Date: Wed, 8 May 2013 10:56:25 +0100
From: stuar...@gmail.com
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] 2.10.1
On Fri, May 3, 2013 at 6:15 PM, Vivian Meazza wrote:
I re-installed the Jenkins nightly Win build from yesterday – seems OK,
although I
On 8 May 2013, at 10:56, Stuart Buchanan stuar...@gmail.com wrote:
I thought 2.10.1 data would be taken from 2.10.0, with commits cherry-picked?
If not, I'd suggest backing out that commit from the 2.10.1 data branch, as
it has a co-requisite simgear change, and as Vivian mentions still has
Stuart
From: Buchanan [mailto:stuar...@gmail.com]
Sent: 08 May 2013 10:56
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] 2.10.1
On Fri, May 3, 2013 at 6:15 PM, Vivian Meazza wrote:
I re-installed the Jenkins nightly Win build from yesterday - seems
OK, although I
Hi Stuart,
Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm
I think I've seen that with all aircraft I've flown recently. IIRC they were
all
non-AAR capable (as in, they had no AAR stuff in -set.xml) but I'm not near
my computer, so I cannot confirm that
If It's an FGRun problem maybe it's caused by the 3D preview code parsing the
planes
From: gijsr...@hotmail.com
To: flightgear-devel@lists.sourceforge.net
Date: Wed, 8 May 2013 20:57:33 +0200
Subject: Re: [Flightgear-devel] 2.10.1
Hi Stuart,
Failed to set alias to /controls/refuelling
-devel] 2.10.1
If It's an FGRun problem maybe it's caused by the 3D preview code parsing
the planes
_
From: gijsr...@hotmail.com
To: flightgear-devel@lists.sourceforge.net
Date: Wed, 8 May 2013 20:57:33 +0200
Subject: Re: [Flightgear-devel] 2.10.1
Hi Stuart,
Failed to set alias
Hi,
Failed to create alias at
/controls[0]/refuelling[0]/refuelling-drogues-pos-norm
[0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing
another
property.
Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm
According Fred's comment in
Am 2013-05-03 19:15, schrieb Vivian Meazza:
Check your IOrules! (write to 'Z:/do-not-access' is allowed)
Check your IOrules! (read from 'Z:/do-not-access' is allowed)
Have you installed a recent fgdata? If so these messages should not appear.
Tom
--
Thomas Geymayer www.tomprogs.at /
Tom
-Original Message-
From: Thomas Geymayer [mailto:tom...@gmail.com]
Sent: 04 May 2013 08:27
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] 2.10.1
Am 2013-05-03 19:15, schrieb Vivian Meazza:
Check your IOrules! (write to 'Z:/do-not-access
Tom
-Original Message-
From: Vivian Meazza [mailto:vivian.mea...@lineone.net]
Sent: 04 May 2013 09:20
To: 'FlightGear developers discussions'
Subject: Re: [Flightgear-devel] 2.10.1
Tom
-Original Message-
From: Thomas Geymayer [mailto:tom...@gmail.com]
Sent: 04 May
On 30 Apr 2013, at 23:22, Saikrishna Arcot saiarcot...@gmail.com wrote:
Are there still any plans to release a 2.10.1?
I've been very busy the past few weeks, but in theory the binaries are done and
exist (on Jenkins) for Windows, Mac and Linux. After some testing, It just
needs 'someone' to
. I will
have a look with XP later if you would like. Unless that is there's been
something since last night .
Vivian
From: James Turner [mailto:zakal...@mac.com]
Sent: 03 May 2013 12:17
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] 2.10.1
On 30 Apr 2013
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Are there still any plans to release a 2.10.1?
- --
Saikrishna Arcot
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
On 3 Apr 2013, at 20:42, geneb ge...@deltasoft.com wrote:
It might be a good idea to create a script that will distribute the new
builds to the various mirrors. That way I'm less likely to throttle the
machine to 10k/sec when it hammers whatever I'm watching on Netflix at the
time. :D
I
Hi,
Continuing with the experimental creation of a bug fix release,
Release-candidate builds for 2.10.1:
http://flightgear.simpits.org:8080/job/Windows-release/
http://flightgear.simpits.org:8080/job/Linux-release/
http://flightgear.simpits.org:8080/job/Mac-release/
Hi James,
This is great news if you are able to crank out full installers right from
Jenkins. That will save me a bunch of downloading and hours of uploading
for every new release candidate.
Thanks,
Curt.
On Wed, Apr 3, 2013 at 4:34 AM, James Turner zakal...@mac.com wrote:
Hi,
On Wed, 3 Apr 2013, Curtis Olson wrote:
Hi James,
This is great news if you are able to crank out full installers right from
Jenkins. That will save me a bunch of downloading and hours of uploading
for every new release candidate.
It might be a good idea to create a script that will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi James,
you could also automatically seed them in BitTorrent, on a Linux box
you can use btmakemetafile which I use here to generate those update
packages on my tracker [1].
Roland
[1]: http://mxchange.org:23456/
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi James,
you could also automatically seed them in BitTorrent, on a Linux box
you can use btmakemetafile which I use here to generate those update
packages on my tracker [1].
Roland
[1]: http://mxchange.org:23456/
-BEGIN PGP SIGNATURE-
On 16 Mar 2013, at 20:49, Pat pat.callah...@gmail.com wrote:
what's the relationship between
2.10.0
the maint branch
and 2.10.1?
2.10.1 will be released from the 2.10 branch, when I start picking commits. I'm
going to bump the version files on the branch 'now' aka once I've had a cup of
On 17 Mar 2013, at 09:27, James Turner zakal...@mac.com wrote:
2.10.1 will be released from the 2.10 branch, when I start picking commits.
I'm going to bump the version files on the branch 'now' aka once I've had a
cup of tea :)
Branches are updated, and the initial fixes I know of / were
On 17 Mar 2013, at 10:33, James Turner zakal...@mac.com wrote:
Any others suggestions are welcome. There was a change Stuart made early
after the 2.10 branch, which I was considering, but I've totally forgotten
what it was now, will dig through the mail archives and see if I can find it.
what's the relationship between
2.10.0
the maint branch
and 2.10.1?
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Hi all,
(2013/03/14 7:11), Frederic Bouvier wrote: With regard to the Windows
release, after installing Setup
Flightgear
2.10.0.3.exe on Windows XP, when launching fgrun I immediately get
the following error/warning:
There is no disk in the drive. Please insert a disk into drive
D:.
Just for reference about how to test.
Following advice in
http://code.google.com/p/flightgear-bugs/issues/detail?id=284#c66
, I launched process monitor from Microsoft, watched file access of
fgrun when dhc2 was selected, and then I got following results:
C:\Program
Just to check, will both Flightgear and Simgear be updated to 2.10.1,
or just Flightgear?
Saikrishna Arcot
On Wed 13 Mar 2013 08:31:40 AM CDT, James Turner wrote:
Hi,
As previously suggested, I am going to attempt a 2.10.1 release, to see if
this improves our perceived quality. There's
Hi James, sounds good, even if there are only a small number (1 or more)
important fixes. Would it make sense to amend our release procedure
(Torsten) :-) to include a subsection on sub-release procedures. Under the
hood we probably repeat most of the full release procedure, but maybe we'd
want
So far I can think of two fixes:
0b04458e99689a30f668d1b37bce93fa55149a2b
b71e703d75d19dff698b38177f319c6baa76a277
Will let you know when I find more.
Gijs --
Everyone hates slow
On 13 Mar 2013, at 13:51, Gijs de Rooy gijsr...@hotmail.com wrote:
0b04458e99689a30f668d1b37bce93fa55149a2b
b71e703d75d19dff698b38177f319c6baa76a277
You know, saying which repository, and a one line description of the fix, would
really save me some typing and git calls :)
James
On 13 Mar 2013, at 13:35, Saikrishna Arcot saiarcot...@gmail.com wrote:
Just to check, will both Flightgear and Simgear be updated to 2.10.1,
or just Flightgear?
All three - simgear, flightgear and fgdata - since the fixes span all three.
James
On Wed, Mar 13, 2013 at 9:31 AM, James Turner zakal...@mac.com wrote:
Hi,
As previously suggested, I am going to attempt a 2.10.1 release, to see if
this improves our perceived quality. There's some bug fixes I am already
aware of, including a Windows path-handling one which is quite
Hi,
- Mail original -
De: Gary Neely grne...@gmail.com
On Wed, Mar 13, 2013 at 9:31 AM, James Turner zakal...@mac.com
wrote:
Hi,
As previously suggested, I am going to attempt a 2.10.1 release, to
see if this improves our perceived quality. There's some bug fixes
I am
With regard to the Windows release, after installing Setup
Flightgear
2.10.0.3.exe on Windows XP, when launching fgrun I immediately get
the following error/warning:
There is no disk in the drive. Please insert a disk into drive
D:.
It does it upon launch of fgrun, and it will
36 matches
Mail list logo
