Re: [Flightgear-devel] Pre-release windows binary
Alex Perry writes: Alex Perry writes: * On a G400 card with lots of memory, I'm getting 4fps out-the-box. This is down from the high 20s previous versions. It improves to 14fps if I get rid of the Textures.high directory temporarily. Thus, the decision making for texture sizing could be better. Is this built --with-logging or --without-logging? Dunno. It was the pre2 prebuilt binary from the Nottingham server ... It was built without logging: CFLAGS=-Wall -O2 CXXFLAGS=-Wall -O2 ./configure --without- logging The JSBSim logging is still output but most of that is not output during actual flight. I get fine framerates with it - they seem to be fill-rate limited at 37fps at 1152x864 on an Athlon 1.2 with Oxygen VX1. On a P350 with a 32MB ATI card (one of the Rage Chipsets - no TL) I get high 30's (probably fillrate limited) most of the time in the UK, dropping into the teens around high polygon areas such as KSFO. I have noticed that some cards get hit very hard at the larger airports (ie KSFO), dropping to low single figures when looking at the airport, but they are generally 8MB cards. Cheers - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Pre-release windows binary
Alex Perry writes: Alex Perry writes: * On a G400 card with lots of memory, I'm getting 4fps out-the-box. This is down from the high 20s previous versions. It improves to 14fps if I get rid of the Textures.high directory temporarily. Thus, the decision making for texture sizing could be better. Is this built --with-logging or --without-logging? Dunno. It was the pre2 prebuilt binary from the Nottingham server ... It was built without logging: CFLAGS=-Wall -O2 CXXFLAGS=-Wall -O2 ./configure --without- logging I have noticed that some cards get hit very hard at the larger airports (ie KSFO), dropping to low single figures when looking at the airport, but they are generally 8MB cards. Yeah, as I tried to imply, I don't think it's the build. If we're making decisions on which textures to use by asking the GL what size it supports, I should point out that many versions state a size that is twice as big as the hardware supports. In that case, the driver makes four passes through the relevant triangles to pick up all four quadrants of the big textures, leading to a massive hit on framerate. Can we have a command line / preferences option to specify whether to use the hires textures as-is or to forcibly ignore the directory? On several of my (linux) machines, I've got a patch in there for that. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Pre-release windows binary
Jon S. Berndt writes: * On a G400 card with lots of memory, I'm getting 4fps out-the-box. This is down from the high 20s previous versions. It improves to 14fps if I get rid of the Textures.high directory temporarily. Thus, the decision making for texture sizing could be better. I remember this happening to me over a period of a couple months about a year ago. Eventually I upgraded my video card. In your case this doesn't sound right or good. Something is wrong. I wish I could try it too but my machine is still in the shop. I hope it's not something in JSBSim, but I don't see what it could be. Was the binary compiled --with-logging or --without-logging? That unfortunately can have a large negative impact on windows performance. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Pre-release windows binary
Alex Perry writes: * On a G400 card with lots of memory, I'm getting 4fps out-the-box. This is down from the high 20s previous versions. It improves to 14fps if I get rid of the Textures.high directory temporarily. Thus, the decision making for texture sizing could be better. Is this built --with-logging or --without-logging? Dunno. It was the pre2 prebuilt binary from the Nottingham server ... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Pre-release windows binary
Alex Perry writes: Alex Perry writes: * On a G400 card with lots of memory, I'm getting 4fps out-the-box. This is down from the high 20s previous versions. It improves to 14fps if I get rid of the Textures.high directory temporarily. Thus, the decision making for texture sizing could be better. Is this built --with-logging or --without-logging? Dunno. It was the pre2 prebuilt binary from the Nottingham server ... Is it dumping a lot of console output when it runs? Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Pre-release windows binary
Alex Perry writes: Dunno. It was the pre2 prebuilt binary from the Nottingham server ... Curt asked: Is it dumping a lot of console output when it runs? It was dumping at least the first dozen screenfuls that I'm used to seeing under Linux ... then I minimized the batch file's window. That probably doesn't help and I'm not near that machine right now - sorry. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
