RealFlight G3 graphics card support

cjshaker said:
After WinXP updates a couple of weeks ago, and some change I made to BIOS, my machine burned up another activation. For some reason, the BIOS decided to remap devices in memory. That caused windows to think that my hardware had changed. I'm not sure how I caused it to do that. I learned about the device addresses changing from the Windows system log. Wanted to know what WinXP was complaining about.


It really should have not done that.

AFAIK the OOBE code only looks for major changes to the system, e.g. MAC address or motherboard serialization.

I've re-imaged a windows install to a new hard drive, then put the new drive into the old system along with a new video card.

Xp came up, found the new drive ( to install the drivers ), asked for the new video drivers, rebooted and all was well with the world.

I wonder if there was a large change to one of the hardware keys, causing the system to assume it was newly installed...

cjshaker said:
Is there some BIOS setting that I could have screwed up which could cause the graphics to run slow in Windows, yet be fast when full screen?

Not really, other than the AGP aperture size, everything is controlled by Windows itself.

Even the motherboard bios and video bios is replaced by a "virtual" one as the system boots.

cjshaker said:
Sounds good. I'll try the Nvidia card soon, if I can't find a problem in my BIOS config.

Good luck!
 
List of hardware changes WinXP saw on my computer

opjose said:
It really should have not done that.

AFAIK the OOBE code only looks for major changes to the system, e.g. MAC address or motherboard serialization.

I've re-imaged a windows install to a new hard drive, then put the new drive into the old system along with a new video card.

Xp came up, found the new drive ( to install the drivers ), asked for the new video drivers, rebooted and all was well with the world.

I wonder if there was a large change to one of the hardware keys, causing the system to assume it was newly installed...



Not really, other than the AGP aperture size, everything is controlled by Windows itself.

Even the motherboard bios and video bios is replaced by a "virtual" one as the system boots.



Good luck!



Thank you again for the help.

Yes, I've also replaced hard disks and restored Windows using Acronis True Image, without burning up an activation. However, I've also changed the graphics card and had WinXP say that my hardware had changed too much since it was activated, and must be reactivated.

Here is the list of hardware changes that I got out of the Windows System log just after WinXP made me reactivate the system. I keep wondering if any of these changes could be causing the slow performance that I'm seeing?

Chris


System Information report written at: 10/10/07 21:02:02

System Name: CJSHAKER-AMD64

[Hardware Resources]



Time Change Name Details Resource Type

10/10/2007 9:00:30 PM CHANGED System board Property "StartingAddress" changed from "1048576" to "0". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Silicon Image SiI 3132 SATALink Controller Property "StartingAddress" changed from "3754949632" to "3754917888". Device Memory Address

10/10/2007 9:00:30 PM CHANGED PCI standard PCI-to-PCI bridge Property "StartingAddress" changed from "3755999232" to "3221225472". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Radeon X1600 Series Property "StartingAddress" changed from "3756916736" to "3221225472". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Texas Instruments OHCI Compliant IEEE 1394 Host Controller Property "StartingAddress" changed from "3758086144" to "3758063616". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "4276092928" to "4273995776". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "4278185984" to "4276097024". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "4289724416" to "4278185984". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "4293918720" to "4289724416". Device Memory Address

10/10/2007 9:00:30 PM CHANGED PCI bus Property "StartingAddress" changed from "655360" to "2147483648". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Radeon X1600 Series Property "StartingAddress" changed from "655360" to "3756916736". Device Memory Address

10/10/2007 9:00:30 PM CHANGED PCI standard PCI-to-PCI bridge Property "StartingAddress" changed from "655360" to "3755999232". Device Memory Address

10/10/2007 9:00:30 PM CHANGED System board Property "StartingAddress" changed from "786432" to "1048576". Device Memory Address

10/10/2007 9:00:30 PM CHANGED PCI bus Property "StartingAddress" changed from "851968" to "655360". Device Memory Address

10/10/2007 9:00:30 PM CHANGED System board Property "StartingAddress" changed from "917504" to "786432". Device Memory Address

10/10/2007 9:00:30 PM CHANGED Standard floppy disk controller Property "StartingAddress" changed from "1015" to "1008". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "114" to "101". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "1232" to "114". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "128" to "1232". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "1280" to "128". Port Resource

10/10/2007 9:00:30 PM CHANGED Direct memory access controller Property "StartingAddress" changed from "129" to "0". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "132" to "1280". Port Resource

10/10/2007 9:00:30 PM CHANGED Direct memory access controller Property "StartingAddress" changed from "135" to "129". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "136" to "132". Port Resource

10/10/2007 9:00:30 PM CHANGED Direct memory access controller Property "StartingAddress" changed from "137" to "135". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "140" to "136". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "1408" to "140". Port Resource

10/10/2007 9:00:30 PM CHANGED Direct memory access controller Property "StartingAddress" changed from "143" to "137". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "144" to "1408". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "16" to "144". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "162" to "16". Port Resource

10/10/2007 9:00:30 PM CHANGED NVIDIA nForce PCI System Management Property "StartingAddress" changed from "1792" to "1536". Port Resource

10/10/2007 9:00:30 PM CHANGED Direct memory access controller Property "StartingAddress" changed from "192" to "143". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "2048" to "162". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "2176" to "2048". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "224" to "2176". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "2304" to "224". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "2432" to "2304". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "2608" to "2592". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "3072" to "2608". Port Resource

10/10/2007 9:00:30 PM CHANGED Programmable interrupt controller Property "StartingAddress" changed from "32" to "160". Port Resource

10/10/2007 9:00:30 PM CHANGED PCI bus Property "StartingAddress" changed from "3328" to "0". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "3328" to "3072". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "34" to "2432". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "34944" to "34816". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "35840" to "34944". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "36864" to "35840". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "36992" to "36864". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "38016" to "37888". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "38912" to "38016". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "39040" to "38912". Port Resource

10/10/2007 9:00:30 PM CHANGED Standard Dual Channel PCI IDE Controller Property "StartingAddress" changed from "39936" to "39040". Port Resource

10/10/2007 9:00:30 PM CHANGED Realtek AC'97 Audio Property "StartingAddress" changed from "41984" to "40960". Port Resource

10/10/2007 9:00:30 PM CHANGED NVIDIA nForce PCI System Management Property "StartingAddress" changed from "44032" to "1792". Port Resource

10/10/2007 9:00:30 PM CHANGED Primary IDE Channel Property "StartingAddress" changed from "496" to "1014". Port Resource

10/10/2007 9:00:30 PM CHANGED Broadcom RAIDCore(tm) Controller Property "StartingAddress" changed from "58496" to "58368". Port Resource

10/10/2007 9:00:30 PM CHANGED Broadcom RAIDCore(tm) Controller Property "StartingAddress" changed from "59392" to "58496". Port Resource

10/10/2007 9:00:30 PM CHANGED Broadcom RAIDCore(tm) Controller Property "StartingAddress" changed from "59520" to "59392". Port Resource

10/10/2007 9:00:30 PM CHANGED Broadcom RAIDCore(tm) Controller Property "StartingAddress" changed from "60416" to "59520". Port Resource

10/10/2007 9:00:30 PM CHANGED ISAPNP Read Data Port Property "StartingAddress" changed from "628" to "2681". Port Resource

10/10/2007 9:00:30 PM CHANGED ISAPNP Read Data Port Property "StartingAddress" changed from "633" to "628". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "68" to "34". Port Resource

10/10/2007 9:00:30 PM CHANGED Secondary IDE Channel Property "StartingAddress" changed from "886" to "368". Port Resource

10/10/2007 9:00:30 PM CHANGED Radeon X1600 Series Property "StartingAddress" changed from "944" to "53248". Port Resource

10/10/2007 9:00:30 PM CHANGED PCI standard PCI-to-PCI bridge Property "StartingAddress" changed from "944" to "53248". Port Resource

10/10/2007 9:00:30 PM CHANGED Radeon X1600 Series Property "StartingAddress" changed from "960" to "944". Port Resource

10/10/2007 9:00:30 PM CHANGED PCI standard PCI-to-PCI bridge Property "StartingAddress" changed from "960" to "944". Port Resource

10/10/2007 9:00:30 PM CHANGED Motherboard resources Property "StartingAddress" changed from "98" to "68". Port Resource
 
cjshaker said:
Thank you again for the help.

Here is the list of hardware changes that I got out of the Windows System log just after WinXP made me reactivate the system. I keep wondering if any of these changes could be causing the slow performance that I'm seeing?

Chris


System Information report written at: 10/10/07 21:02:02

System Name: CJSHAKER-AMD64

Wow, it seems that Windows performed an almost complete rediscovery of the hardware resources.

Almost as if SYSPREP was run to "re-seal" your computer.

In spite of this OOBE should not have burned a validation... unless something corrupted both the primary and backup hardware registy hiearchy.

e.g. a memory fault?


There was a lot of shifting of I/O memory mapping, so it is quite conceivable that you may have an undiscovered overlap, causing slow performance of the video card.

You would have to force a smaller "reshift"...

In this case I would yank the video card and let windows come up with any on board adapters.

If this is not present, I put in a PCI card temporarily to let the system boot.

Then I remove the existing ATI drivers, reboot, then shut down.

( at worst I've gone through the registry at this point and have removed references to the now "phantom" hardware if possible... )

Install the card back in, and re-install the drivers.
 
Not sure what happened

I don't know quite what triggered the change.

I checked the address map configuration items in the BIOS, and they appear to be set to their defaults, according to the ASUS A8N32-SLI Deluxe manual. Thought maybe I had played with one of them.

I'll try to report the problem to Microsoft...

Chris



opjose said:
Wow, it seems that Windows performed an almost complete rediscovery of the hardware resources.

Almost as if SYSPREP was run to "re-seal" your computer.

In spite of this OOBE should not have burned a validation... unless something corrupted both the primary and backup hardware registy hiearchy.

e.g. a memory fault?


There was a lot of shifting of I/O memory mapping, so it is quite conceivable that you may have an undiscovered overlap, causing slow performance of the video card.

You would have to force a smaller "reshift"...

In this case I would yank the video card and let windows come up with any on board adapters.

If this is not present, I put in a PCI card temporarily to let the system boot.

Then I remove the existing ATI drivers, reboot, then shut down.

( at worst I've gone through the registry at this point and have removed references to the now "phantom" hardware if possible... )

Install the card back in, and re-install the drivers.
 
Reported to DirectX team, and to ATI/AMD

I submitted a problem report to the Microsoft DirectX team, and opened a trouble ticket with the ATI/AMD support people as well.

Chris Shaker
 
The AMD/ATI people responded to my trouble ticket this morning with:

3D processing is DISABLED when running a 3D application in Window Mode.
This is as per design.

Am I dreaming when thinking that it used to work for me? Is the above true for Nvidia cards?

Chris Shaker



cjshaker said:
I submitted a problem report to the Microsoft DirectX team, and opened a trouble ticket with the ATI/AMD support people as well.

Chris Shaker
 
Hi all,

i have a brand new mac pro with a NVIDIA GeForce 7300 GT

and i always received a error creating shadow error, is there a way to fix that


Thx all
 
cjshaker said:
The AMD/ATI people responded to my trouble ticket this morning with:

3D processing is DISABLED when running a 3D application in Window Mode.
This is as per design.

Am I dreaming when thinking that it used to work for me? Is the above true for Nvidia cards?

Chris Shaker

What a crock! Someone is really giving you a bunch of B.S.

That violates the DX specifications.

Many of us run G3 in "windowed" mode on many different 3D cards.

Many games would not work otherwise nor would many of the 3D screensavers, etc.

I've run G3 and many other programs in windowed mode on my ATI All-in-one 9700 which is not a fantastic 3D card and only has 128 megs.

If what they told you were true, they would have NO market as everyone would purchase fully compliant cards.

Typical crapola.
 
Can anyone help with any information dealing with this card:

HIS Hightech H155HMF256EL1N

My computer has a PCI slot and a PCIe 1X dhk79 has been helping me find a card (which there seem to be very few for the PCIe 1x style slot)

My question is: Will the ATI Radeon X1550 chipset work with G3.5 or more importantly G4?? Or will there be "texture problems" like the:

Radeon X1300
Radeon X1600
Radeon X1800

Thanks for any information
 
Bummer!

Well I just bought G3.5, big surprise video not supported. Why not just ship a freakin' card that works with the software? .

Why not just make it "fly" well and not look so pretty?

Will this work?
GPU: NVIDIA® GeForce™ FX 5500
Bus Type: AGP
Memory: 256MB DDR
Core Clock: 270MHz
RAMDACs: Dual 350MHz
API Support: Microsoft® DirectX® 9.0 and lower, OpenGL 1.5 and lower for Microsoft® Windows®
Connectors: VGA, S-Video Out
Vertices/Sec.: 67.5 million
NVIDIA® GeForce™ FX 5500 at a Glance
AGP 8X/4X/2X compatible
Up to 4 pixels per clock rendering engine
Up to 16 textures per pass
Digital Vibrance Control™ 3.0
Microsoft® DirectX® 9.0 with Vertex Shader 2.0 and Pixel Shader 2.0
NVIDIA® CineFX™ Engine

OR this $119
GPU: NVIDIA GeForce 7300 GT
Video Memory: 512MB DDR2
Core Clock: 350MHz
Vertices: 350 million/sec.
Bus Type: AGP
Connectors: DVI-I, VGA + HDTV
Multiple Monitor Support: Yes
HDCP: No
RAMDACs: Dual 400MHz
 
Last edited:
AeroFly Pro and FMS work in a window

What's wierd is that FMS and AeroFly Professional are working great in a window...

Chris Shaker



opjose said:
What a crock! Someone is really giving you a bunch of B.S.

That violates the DX specifications.

Many of us run G3 in "windowed" mode on many different 3D cards.

Many games would not work otherwise nor would many of the 3D screensavers, etc.

I've run G3 and many other programs in windowed mode on my ATI All-in-one 9700 which is not a fantastic 3D card and only has 128 megs.

If what they told you were true, they would have NO market as everyone would purchase fully compliant cards.

Typical crapola.
 
cjshaker said:
What's wierd is that FMS and AeroFly Professional are working great in a window...

Chris Shaker


Yup, something like a "particle effects" ( I'm choosing one at random to illustrate... ) is not working in Windowed mode for you but does in full screen.

Programs which do use this effect revert to software only 3D in windowed mode, such as G3.

This is a problem with the driver ( POSSIBLY a limitation of the card, but wow, that would be a serious failing on the part of the hardware people... ).
 
Got hosed changing video cards

I used 'Add/Remove Programs' to remove the ATI video drivers, then swapped out the ATI X-1600 Pro HDMI card for a new ASUS EN8600GT card. When I tried to boot windows, it would hang in the discovered new hardware phase. Even in safe mode, even in safe mode command console. Well and truly hosed. A little parting gift from ATI.

Wiped out the hard disk, and installed a new Windows Vista Home Premium. Updated, installed RealFlight G3, updated it, installed the four Expansion Packs. It's happily flying 3D smoothly in a window, flying great.

Decided to start collecting a little data.

Realflight G3 (latest version 3.50.065) on my Acer latop, an Aspire 3680, running Windows Vista Basic, with Mobile Intel 945 Express Chipset Family display works great! Smooth and fast when running in a window.

My older desktop machine, 3 Ghz P4, with Radeon 9600, running latest WinXP Home SP2 (latest updates) runs RealFlight G3 in a window just fine, too. Fast and smooth.

I agree with you, ATI/AMD is BSing me about 3D in a window not being a design feature!

Chris Shaker
 
Need help on G3.5 graphics card

I bought G3.5 yesterday and am confused about which video card works best.
Choices available:
1) MSI NVIDIA GeForce NX 6600 GT 256MB DDR3
2) ATI
Thanks for any advise.
Ryan
 
If you can use 6600 GT on your system, consider a 8600 GT instead.

They run only a few dollars more but are more "current" and run at a faster rate.

newegg.com and others have very good prices on them.
 
g3.5 video card recomended

Hi

If you are like me older system (AGP) try to get a nvidea 7800gs agp card. Can turn everything to highest except shadows (High) streamers (High). Works great be warned you need a hefty power supply, 450 watts or more. Used the overclocking utility that came with new nvidea driver, (let it set max.)

System:
Windows XP sp2
1 gb ram
7800gs AGP overclocked ~ 25% 1680 x 1050 ~60 fps 32bit color
AMD Athlon XP 3200+

PS I only use the photofields, cpu I think to slow run 3d fields at this resolution
Hope this helps
 
the 8800 series cards should be added to the list, i am using an EVGA 8800GTS 640 Mb and it works awesome. i am using g3 (updated to g3.5) and i believe that 8800's and up will work just as well for G4.
 
ryansn said:
I bought G3.5 yesterday and am confused about which video card works best.
Choices available:
1) MSI NVIDIA GeForce NX 6600 GT 256MB DDR3
2) ATI
Thanks for any advise.
Ryan

i would use an nvidia graphics based card, ever since amd bought ati the ati cards have been a little lacking IMHO. if you have a pci-x16 slot i recommend an 8800 or better (run everything at max settings) however frame rates will drop in multiplayer and this is not because of the card but i feel more to do with the server. i can run at max settings all day long but once i get into multiplayer frame rates drop as more people enter. again NOT a graphics card issuebecause once out of multiplayer i am back up in the 98 and up frame rates and this with a stock non overclocked system with a pentium D950 cpu. :D
 
Back
Top