Latest progress report...
Got the new quad 4 machine up and running
3 instances of fg running, one master two slaves using 127.0.0.1:550x as
the network interface. Flying (simming) is fun again ;-)
Took a bit of brain storming organizing/editing the xml files to bind each
fg instance to a di
On Tue, Feb 8, 2011 at 10:05 PM, henri orange wrote:
> Will it solved the Boeing314 issue ?
The Boeing314 in GIT doesn't even get that far, it is missing a file
"Nasal/Boeing314-limits.xml"
Commenting the reference out, the aircraft at least takes off.
--
Csaba/Jester
-
On Tue, Feb 8, 2011 at 9:27 PM, Torsten Dreyer wrote:
>> And that is because of the hardcoded default of 8 fuel tanks. Attached
>> patch makes sure at least the existing tanks are covered by the
>> properties.
>>
> Thanks for spotting this. I was naive enough to think no aircraft ever has
> more t
Will it solved the Boeing314 issue ?
2011/2/8 Torsten Dreyer
> > And that is because of the hardcoded default of 8 fuel tanks. Attached
> > patch makes sure at least the existing tanks are covered by the
> > properties.
> >
> Thanks for spotting this. I was naive enough to think no aircraft ever
Hello Henri,
Am 07.02.2011 18:38, schrieb henri orange:
> [...] I am getting ( randomly ) the following messages
>
> Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..)
> nan nan nan nan nan nan segment ignored..
I've looked into this a bit. It seems again to hav
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottleneck
> We have curently no better simulation of that, even the S76 by Syd which
> uses a different code, is affected.
The problem is that for some reason the configured fuel-density does not reach
the TankProperties class but stays at zero, resulting in division by zero in
the nasal-based engine/fuel
On 08.02.2011 20:40, Torsten Dreyer wrote:
> No sweat - 2.2.0 is not affected. This is because of the TankProperties
> I'll try to come up with a solution but that might not be before the weekend.
And, always seeing the positive side, this might be a great opportunity
to have more people testing
> And that is because of the hardcoded default of 8 fuel tanks. Attached
> patch makes sure at least the existing tanks are covered by the
> properties.
>
Thanks for spotting this. I was naive enough to think no aircraft ever has
more then eight tanks. Now TankProperties are created for every con
Hi,
> No sweat - 2.2.0 is not affected. This is because of the
> TankProperties
> update. Looks like there are an awful lot of places where
> people computed
> fuel-levels and fuel-weights and converting from/to
> imperial/us/metric units
> :-P
>
> I'll try to come up with a solution but that
> Hi,
>
> trying out the bo105 today with latest GITt I noticed a new Bug which
> prevent using any of our helicoters:
>
> http://code.google.com/p/flightgear-bugs/issues/detail?id=266&sort=-id
>
> With this bug I can't go on currently on developing my helicopters for
> FGFS, but the main pint
Hello Henri,
Am 07.02.2011 18:38, schrieb henri orange:
> [...] I am getting ( randomly ) the following messages
>
> Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..)
> nan nan nan nan nan nan segment ignored..
I've looked into this a bit. It seems again to hav
On Tue, 8 Feb 2011, Curtis Olson wrote:
> I made a commit into a branch of a --local clone of my fgdata repository. I
> pushed that to the matching branch in my main fgdata.git repository.
>
> Then I attempted to merge one commit into the master branch ... however it
> merged *all* my changes.
>
Hi,
trying out the bo105 today with latest GITt I noticed a new Bug which prevent
using any of our helicoters:
http://code.google.com/p/flightgear-bugs/issues/detail?id=266&sort=-id
With this bug I can't go on currently on developing my helicopters for FGFS,
but the main pint is the Bo105 is t
I made a commit into a branch of a --local clone of my fgdata repository. I
pushed that to the matching branch in my main fgdata.git repository.
Then I attempted to merge one commit into the master branch ... however it
merged *all* my changes.
How can I back this out (I've made some hacks to so
Hi,
Not only with the relocation to a mooring position, though that feature is
randomly making the issue.
I cannot explain why, and cannot reproduce twice the same.
I guess the reset sequence/speed is the cause of the issue, scenery ?
model ? fdm ? constant values ?.
The relocation to a mooring
Thanks Jacob,
I will check it out as its easier than my script to build command lines with
the unique machine IO configs.
Harry
On Tue, Feb 8, 2011 at 12:32 PM, Jacob Burbach
wrote:
> I think what your looking for is the --config option, it allows you to
> load arbitrary xml config files. S
17 matches
Mail list logo
