Hi Martin and Olivier,
I thought that windturbine orientation was correct in the past -- so please
use due diligence to identify if the problem is just a misorientaiton of
the base model, or if one of the components of the wind vector was reversed
(or the code that takes the wind(east) and
Curtis Olson wrote:
I thought that windturbine orientation was correct in the past -- so please
use due diligence to identify if the problem is just a misorientaiton of
the base model, or if one of the components of the wind vector was reversed
(or the code that takes the wind(east) and
On Mon, 27 Feb 2012 09:54:40 -0600, Curtis Olson wrote:
Hi Martin and Olivier,
I thought that windturbine orientation was correct in the past -- so
please use due diligence to identify if the problem is just a
misorientaiton of the base model, or if one of the components of the
wind vector
Jon Stockill wrote:
It may be from people submitting positions with an incorrect heading
set. Since the model obviously turns into wind the heading should be 0
in the database, though this appears as 180 in the stg file. If
someone's submitted a hand crafted stg file with all the headings
Hi
Fred!
I'm sending the
filept.po
updated with the
translation FGRUN into
Portuguese.
Regards,
Lizandro Falco
# Portuguese translations
On Mon, Feb 27, 2012 at 11:37 AM, Martin Spott martin.sp...@mgras.netwrote:
Jon Stockill wrote:
It may be from people submitting positions with an incorrect heading
set. Since the model obviously turns into wind the heading should be 0
in the database, though this appears as 180 in the
Curtis Olson wrote:
On Mon, Feb 27, 2012 at 11:37 AM, Martin Spott martin.sp...@mgras.netwrote:
What about introducing .ttg as a new file format in FlightGear - t
as *t*rue heading and because t is the successor to s :-)
This would get rid of a big of annoyance in FG Scenery land.
Really? Originally this was setup to be true heading -- I wonder when that
got changed and if it was an intentional change or a mistake that wasn't
caught at the time?
Curt.
On Mon, Feb 27, 2012 at 12:35 PM, Martin Spott wrote:
Curtis Olson wrote:
On Mon, Feb 27, 2012 at 11:37 AM, Martin
I am pleased to announce the creation of a new FlightGear mailing list
dedicated to all things scenery related: GIS, code, content, licenses,
modeling, artwork, etc.
The goal is to try to pull together our developers, modelers, and artists
who are working on scenery or who have an interest in
Curtis Olson wrote:
Really? Originally this was setup to be true heading -- I wonder when that
got changed and if it was an intentional change or a mistake that wasn't
caught at the time?
I don't have an idea, why - maybe that's been the default in PPE, AC3D
or whichever tool. Jon made me
Martin Spott wrote:
I don't have an idea, why - maybe that's been the default in PPE, AC3D
or whichever tool. Jon made me aware of this issue many years ago
(when we started filling the scenery objects database) and, as far as I
remeber, I found evidence that Jon is right.
BTW, from my
Hello,
just checked the orientation of the windturbine.ac and windsock.ac (windsock
is working correct) with blender:
windsock in +y
|
|
|
---
windturbine in -y
|
|-|
| |
|
|
--
That's correct, because the windsock faces out of the wind and the turbine
into the wind.
The
Spotted this and figured Fred or other cmake guru might want to know about
it.
g.
D:\FGFSReleaseBuild\build-sgcmake ..\simgear -G Visual Studio 10
-DMSVC_3RDPARTY_ROOT=D:\FGFSReleaseBuild
-DCMAKE_INSTALL_PREFIX:PATH=D:\FGFSReleaseBuild/install/msvc100/SimGear
-- version is 2 dot 6 dot 0 --
Interesting -- if smoke is also going the wrong way, maybe a bug was
recently introduced with wind/environment?
On Mon, Feb 27, 2012 at 3:09 PM, D-NXKT wrote:
Hello,
just checked the orientation of the windturbine.ac and windsock.ac(windsock
is working correct) with blender:
windsock in +y
It appears that the windows-release target rebuilds _everything_
regardless of whether or not it's necessary. This build gets triggered
multiple times for some reason and due to disk thrashing, renders the
machine basically unusable until it's done. Since this machine also hosts
the VM that
Hi Gene,
It appears that the windows-release target rebuilds _everything_
regardless of whether or not it's necessary. This build gets
triggered multiple times for some reason and due to disk
thrashing, renders the machine basically unusable until it's done.
Since this machine also
16 matches
Mail list logo
