[Flightgear-devel] Re: progress of dc-3 3d cockpit

2004-01-09 Thread Melchior FRANZ
* Ilja Moderau -- Friday 09 January 2004 21:59: > It is a 2d-panel, but it shines through the fuselage, so I removed > it for a short time. If it weren't for a short time only, I'd call this a not so bright idea. fgfs is a flight simulator. It is for flying the dc3, not for watching it fly from o

Aw: [Flightgear-devel] Re: progress of dc-3 3d cockpit

2004-01-09 Thread Ilja Moderau
It is a 2d-panel, but it shines through the fuselage, so I removed it for a short time. > > The new dc3 doesn't have a panel any more. Did you leave out too much? -- Men canĀ“t fly? http://home.arcor.de/iljamod/fly.jpg __

[Flightgear-devel] Re: progress of dc-3 3d cockpit

2004-01-07 Thread Melchior FRANZ
* Erik Hofman -- Wednesday 07 January 2004 15:13: > There was no panel before I left those files out, and > the images don't show a panel either. So we don't have a panel any more, but we have seats! ;-) m. PS: the seats are beautiful ___ Flightgea

Re: [Flightgear-devel] Re: progress of dc-3 3d cockpit

2004-01-07 Thread Erik Hofman
Melchior FRANZ wrote: * Erik Hofman -- Wednesday 07 January 2004 14:38: I've put it in CVS for everybody. There's one thing though, you sent some configuration files (dc3/dc3.xml and dc3/dc3-yasim-set.xml) that contain old settings so I've left them out of CVS. The new dc3 doesn't have a panel

[Flightgear-devel] Re: progress of dc-3 3d cockpit

2004-01-07 Thread Melchior FRANZ
* Erik Hofman -- Wednesday 07 January 2004 14:38: > I've put it in CVS for everybody. There's one thing though, you sent > some configuration files (dc3/dc3.xml and dc3/dc3-yasim-set.xml) that > contain old settings so I've left them out of CVS. The new dc3 doesn't have a panel any more. Did you

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread Jim Wilson
James Turner <[EMAIL PROTECTED]> said: > One valuable thing would be to define the 'input' property nodes the > auto-pilot code will have, so I know what I should be setting. > *Ideally*, thus would be broken down into LNAV / VNAV / auto-throttle > stuff (with some coupling, obviously, especially

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread James Turner
ahOn Mon, 2002-06-10 at 15:58, Jim Wilson wrote: > James Turner <[EMAIL PROTECTED]> said: > > > (I want to get the flight-plans hooked up to the existing > > auto-pilot code, which isn't really designed to look like a 'big jet' > > model of course, though it seems you already have code *somewhe

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread John Wojnaroski
James Turner wrote: > Anyway, I'd like to work out a plan of attack to avoid too much > duplication. I suspect some might be inevitable, since there's slight > different goals. (and, alas, I only have one computer, so I'm kind of > anti the whole 3 computers thing :-) My sense is that any duplica

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread John Wojnaroski
> Hmm, this is going to get fiddly. I've got a generic route/flight-plan > backend sort of working (no flight traversal or waypoint sequencing as > of yet), which I am planning to extend with airways, SIDs, STARs and so > on (with editing of course). The long term plan was to build an FMC / > M

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread Jim Wilson
James Turner <[EMAIL PROTECTED]> said: > (I want to get the flight-plans hooked up to the existing > auto-pilot code, which isn't really designed to look like a 'big jet' > model of course, though it seems you already have code *somewhere* that > handles LNAv and VNAV functions... hmm. You mi

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread Dave Tessman
Its a bit pricey, but I am partial to EDAS, because it is Ethernet based. http://www.edasce.com - Original Message - From: "Gene Buckle" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 10, 2002 7:05 AM Subject: Re: [Flightgear-devel] Re: progre

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread Gene Buckle
> I've spent a little time looking at the EPIC and FSUIPC stuff, but haven't > really > looked at how to make a compatible interface with OpenGC and FG sockets. You might want to look into http://www.phidgets.com. He's building a 256 input device for $50. All of his stuff is USB and he's worki

[Flightgear-devel] Re: progress

2002-06-10 Thread Melchior FRANZ
* James Turner -- Monday 10 June 2002 11:09: > (and, alas, I only have one computer, so I'm kind of > anti the whole 3 computers thing :-) ACK. I've only one here, too, and that won't change any time soon. Well, there's an Atari ST, but ... and then, opengc doesn't even compile on my machine bec

Re: [Flightgear-devel] Re: progress

2002-06-10 Thread James Turner
On Monday, June 10, 2002, at 05:35 am, John Wojnaroski wrote: > Well, I've been working on a Multi-function Control Display Unit (MCDU) > which connects to the FMC and > provides manual control of the nav receivers and other aircraft systems. > Next major effort is adding ability to > insert an

[Flightgear-devel] Re: progress

2002-06-09 Thread John Wojnaroski
> Hi, > > Just wanted to let you know that I haven't disappeared. I've been quite > busy at work the last two weeks and haven't had a lot of free time. I'm > shooting for posting a new Windows alpha executable and a tar of the source > presuming Linux is building ok this weekend. > > Any news on