RE: [Flightgear-devel] Re: Blank screen implementation
Harald JOHNSEN wrote: > I have another probleme with wincvs. > In the list of files in the explorer nearly all files have an 'unknown' > state. So i don't have the diff choice when I right click on them. > I've tried an update with the command line but that does not chance > anything. Its a fresh install of wincvs 2.x but I had the same with the > 1.3. > > Harald. > I'm absolutely not a WinCVS guru. What I know about it has been learned mostly by trial and error (some of the former and lots of the latter). The documentation, shall we say, leaves a lot to be desired. So here goes. What are the extensions of the unknown status files? Many files in the source code are generated by the compiler, and are therefore not in the repository (sorry, BGOTO) extensions .a, .o .exe fall into this category. Files which you have generated and are not in the repository also have the status unknown. Some editors spew these like crazy; they are hidden in windows explorer, but not in WinCVS. Try selecting a directory (make sure it's not one in which you have modified files - that's not fatal, but recovering your work is a darned nuisance -, then Modify > Update. On the update screen select 'create missing directories' and 'get the clean copy'. See what happens. Next, open some directory in windows explorer and delete the files which have status unknown (but are not .a .o. or .exe) See what happens - they should get the status missing. (If they don't they are probably not in the repository in the first place.) Then try the above again to restore them. Finally, if none of this addresses the problem, you can always delete the directories and start over. I've had to do that several times when my copy and the cvs copy just got too far out of line. The good thing about the later versions of WinCVS is that it pretty much works, but it's not all that intuitive and takes some figuring out. Hope none of this is teaching grandmother to suck eggs. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
Vivian Meazza wrote: Drew wrote Ah...that's alright, I'll just stick with what I have. I was told it was a few mouse clicks, and it's already taken more of my time that it's worth. All I'm really trying to do is draw a black rectangle. Thanks for your help. No problem, pity you can't make it work - it really is a boon during development. But you are right not to waste time on it. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d I have another probleme with wincvs. In the list of files in the explorer nearly all files have an 'unknown' state. So i don't have the diff choice when I right click on them. I've tried an update with the command line but that does not chance anything. Its a fresh install of wincvs 2.x but I had the same with the 1.3. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
Drew wrote > Ah...that's alright, I'll just stick with what I have. I was told it > was a few mouse clicks, and it's already taken more of my time that > it's worth. All I'm really trying to do is draw a black rectangle. > > Thanks for your help. No problem, pity you can't make it work - it really is a boon during development. But you are right not to waste time on it. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
Ah...that's alright, I'll just stick with what I have. I was told it was a few mouse clicks, and it's already taken more of my time that it's worth. All I'm really trying to do is draw a black rectangle. Thanks for your help. Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New 3d clouds
Harald JOHNSEN wrote: - fog bug : ok I think I have not re-enable fog Sort of. The terrain seems to be hidden by fog at the appropriate range, but any objects appear to have infinite visibility, so they appear to "float" until the ground eventually comes into view beneath them. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
> -Original Message- > From: [EMAIL PROTECTED] [mailto:flightgear-devel- > [EMAIL PROTECTED] On Behalf Of Drew > Sent: 25 April 2005 16:57 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] Re: Blank screen implementation > > > Have you set the home directory in Admin > preferences? > > I hadn't, but I just did...I assume this is the directory in which the > source trees get saved? Yes - removing it here produced the grey-out entries, but I can't reproduce the file error. > It says to read the documentation, but I > can't find the documentation. They are under Help > CVS Documentation If they aren't do you have an incomplete installation? Do you have a (hidden) file cvspass somewhere on your system? This might be the missing file, but that's a WAG. > > Anyway, adding a home directory didn't change anything. I still get > the same error. > I think it might be uninstall and reinstall time. I have no other ideas. All I can say is that it's worked here for several years, and that I downloaded and installed the latest version a couple of days ago. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
> Have you set the home directory in Admin > preferences? I hadn't, but I just did...I assume this is the directory in which the source trees get saved? It says to read the documentation, but I can't find the documentation. Anyway, adding a home directory didn't change anything. I still get the same error. Thanks, Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Nasal advice...
* Andy Ross -- Monday 25 April 2005 16:01: > setprop(name, setbit(getprop(name), 2)); > > Look more elegant than bit twiddling to my eyes... I found a better solution already. Thanks. > > The problem is that in joystick files I don't have the > > possibility to initialize bit fields or define bit operations. > > Stick the bit stuff (which clearly isn't joystick-dependent) in > globals.nas. Problem solved. Sure. I just thought it would be appropriate to mention this on the developers list, before I stuff anything anywhere. If this was off topic, then I apologize. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Nasal advice...
I wrote:
> Write a function to [...]. Compose them appropriately to set bits
> in numbers. Probably four lines of code,
Turns out it's three lines of code:
n2s = func(n) { var s = buf(6); setfld(s, 0, 48, n); return s; }
getbit = func(n, b) { getfld(var s = n2s(n), b, 1) }
setbit = func(n, b) { setfld(var s = n2s(n), b, 1); return fld(s, 0, 48); }
These guys provide 48 bits in a number. You can theoretically stretch
that to 53, but it requires some fiddling of the doubles that I don't
want to promise yet. :)
Obviously you can't use this yet, because I haven't written the
underlying bit functions. But hopefully this will address the
elegance issues.
Andy
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New 3d clouds
Hello Roman, "Roman Grigoriev" wrote: > [...] (all cards supports them) I'm a bit cautious about your "all cards " statement. Does this include every OpenGL-1.1 platform ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Nasal advice...
Melchior FRANZ wrote: > Wouldn't work in my case. Would only make it even less > elegant. Then I better stick with this: Only if you don't want to write your own functions (in which case every feature I don't want to support is going to be inelegant and you'll never win until I turn Nasal into another monstrosity like perl). Write a function to turn a number into a 4 byte string (or more, you technically can do up to 6 in an IEEE double). Write a function to set or get a bit in a string. Write a function to turn a 4 byte string into a number. Compose them appropriately to set bits in numbers. Probably four lines of code, and you can do: setprop(name, setbit(getprop(name), 2)); Look more elegant than bit twiddling to my eyes... > The problem is that in joystick files I don't have the > possibility to initialize bit fields or define bit operations. Stick the bit stuff (which clearly isn't joystick-dependent) in globals.nas. Problem solved. Once again, bit operations on floating point numbers won't work like you want them to. Think about implementing sign extension in shifts, or rotations, or even (off the top of your head) tell me how many bits are retained when you left shift. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] jidvolo announce
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. I should announce that jidvolo is out. jidVolo is a flight simulator, based on JSBSim and flightgear too. A couple of colleagues and I developed jidVolo aiming to complete a university course in Virtual reality and computer animation. We wanted a realistic flight simulator to fly in our country (yes, virtually :-) ). Since we weren't able to get Italy maps (and height maps) we got those from Massachussets. jidVolo uses JSBSim to simulate the flight, and FlightGear models. We have reached our aim: jidvolo is realistic, to a certain degree :-) If you like to try it, or simply see the screenshots, take a look at the project homepage: http://sourceforge.net/projects/jidvolo There you can find informations, source code and binaries too. (we have got it for Windows, Linux and Linux/ppc). I regret that the documentation included is pretty old and inadeguate. As an errata corrige, I should say that no line option is required. We have tested jidvolo only with Cessna family aircrafts. We should also thank FlightGear team for producing a so complete work. Slainte, iago -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCbNZ3PXQrJUUnLVoRAszqAJ93l9ULynkG4cH9JdMCio00uDZgpgCfRFEo izNhG3009NeOnIuNdmLB+ro= =FQJV -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
Drew wrote > -Original Message- > From: [EMAIL PROTECTED] [mailto:flightgear-devel- > [EMAIL PROTECTED] On Behalf Of > Sent: 25 April 2005 09:20 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] Re: Blank screen implementation > > It prompted me to install python when I first ran it, so I did install > python. Not Pearl, though. Yes, I have version 2.0.0.2 build 2. > Have you set the home directory in Admin > preferences? V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
It prompted me to install python when I first ran it, so I did install python. Not Pearl, though. Yes, I have version 2.0.0.2 build 2. On 4/25/05, Vivian Meazza <[EMAIL PROTECTED]> wrote: > Drew wrote > > > > > > To login use Admin > Login then ... at the bottom right of the login > > screen > > > to access the editing facility. Select: > > > > > > Protocol - pserver > > > Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9 > > > Keywords - Username - use 'Edit' to enter cvsguest > > > - Password - use 'Edit' to enter guest > > > OK to enter all that, then OK to login on the login screen > > > > > > This will log you in - I've just done it > > When I go to Admin->Login, I just get a window that has a CVSROOT > > field at the bottom (empty). There's a button with an ellipsis on it, > > and when I select that, I can see the settings you mention, but they > > are greyed out...uneditable (and blank). > > > > > Alternatively on Admin > Command line enter: > > > > > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 > > login > > > > > > and only that > > > > > > then enter guest as the password when the splash screen is displayed > > I didn't get any splash screen or login prompt...only the same error > > message "Unable to initialize the CVS process: The system cannot find > > the file specified. > > > > I can't duplicate that which you describe. Perhaps a duff installation? Do > you have Python or Perl installed? Are you using WinCvs 2.0.0.2 build 2? > > Regards, > > Vivian > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
Drew wrote > > > To login use Admin > Login then ... at the bottom right of the login > screen > > to access the editing facility. Select: > > > > Protocol - pserver > > Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9 > > Keywords - Username - use 'Edit' to enter cvsguest > > - Password - use 'Edit' to enter guest > > OK to enter all that, then OK to login on the login screen > > > > This will log you in - I've just done it > When I go to Admin->Login, I just get a window that has a CVSROOT > field at the bottom (empty). There's a button with an ellipsis on it, > and when I select that, I can see the settings you mention, but they > are greyed out...uneditable (and blank). > > > Alternatively on Admin > Command line enter: > > > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 > login > > > > and only that > > > > then enter guest as the password when the splash screen is displayed > I didn't get any splash screen or login prompt...only the same error > message "Unable to initialize the CVS process: The system cannot find > the file specified. > I can't duplicate that which you describe. Perhaps a duff installation? Do you have Python or Perl installed? Are you using WinCvs 2.0.0.2 build 2? Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
Thanks for the reply. > To login use Admin > Login then ... at the bottom right of the login screen > to access the editing facility. Select: > > Protocol - pserver > Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9 > Keywords - Username - use 'Edit' to enter cvsguest > - Password - use 'Edit' to enter guest > OK to enter all that, then OK to login on the login screen > > This will log you in - I've just done it When I go to Admin->Login, I just get a window that has a CVSROOT field at the bottom (empty). There's a button with an ellipsis on it, and when I select that, I can see the settings you mention, but they are greyed out...uneditable (and blank). > Alternatively on Admin > Command line enter: > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login > > and only that > > then enter guest as the password when the splash screen is displayed I didn't get any splash screen or login prompt...only the same error message "Unable to initialize the CVS process: The system cannot find the file specified. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
Drew wrote > I'm trying this now with wincvs. I click Admin->Command Line, and > then enter the following string: > > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login > CVS passwd: guest > > When I hit 'ok', it comes back with "Unable to initialize the CVS > process. The system cannot find the file specified" > > There are also some instructions I found on using CVS with Windows on > the FlightGear site, but it refers to commands with umn.edu addresses, > which does not correspond with the page it links to (flightgear.org). > So now I'm confused by this as well. > > Someone please help me out. > To login use Admin > Login then ... at the bottom right of the login screen to access the editing facility. Select: Protocol - pserver Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9 Keywords - Username - use 'Edit' to enter cvsguest - Password - use 'Edit' to enter guest OK to enter all that, then OK to login on the login screen This will log you in - I've just done it Alternatively on Admin > Command line enter: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login and only that then enter guest as the password when the splash screen is displayed HTH Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New 3d clouds
Hi guys! Seen new clouds code but to be it need some tweaks to work perfectly 1) use pointsprites to render impostors because they are quads (all cards supports them) 2) use FBO to reder-to-texture it gives us speedup.(all cards supports them) 3)use at least ARB vertex programs (will work on geforce3) to calculate lighting and billboard transformations 4) use ARB fragment programs (will work on geforceFX) for hardware blending. But clouds looks good to tweak them out :) Roman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Bump-mapping ground textures
I've done bumpmapping+ parralax mapping for flightgear http://fgfs.narod.ru/fgfs12.jpg but it needs on ARB vertex and fragment programs but it needs at least geforceFX fgfs developers wait for a while to include it in CVS but I think that it will be never done :( - Original Message - From: "Frederic Bouvier" <[EMAIL PROTECTED]> To: "FlightGear developers discussions" Sent: Sunday, April 24, 2005 1:49 PM Subject: Re: [Flightgear-devel] Bump-mapping ground textures > Selon Lee Elliott : > > > Hello all, > > > > just curious - are the ground textures bump-mapped? > > No. Bump mapping requires at least multi texturing. There are 2d clouds with > bump mapping, and it was done behind plib. > > -Fred > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Nasal advice...
* Melchior FRANZ -- Monday 25 April 2005 08:47: > The problem is that in joystick files I don't have the possibility to > initialize bit fields or define bit operations. Bindings in joystick > files are executed in "random" order. None is guaranteed to be triggered > at the very beginning. (Although, maybe the part of the first > button binding could be used for that. I'll look into that ...) Yes, this seems to work. Initialize joystick xml variables in the part of button 0 and store them in, for instance, the "controls" namespace (because bindings in joystick files don't even seem to have a common namespace by themselves). m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
