|
Author
|
Topic: Mighty, MH - V5500 still locks SDOE in Glide wih latest drivers
|
Yardstick Pilot
|
posted 07-26- 08:51 AM
Well the new V5500 drivers don't seemed to have addressed the problems I have experienced with SDOE.On the V5500, SDOE previously would only work with Glide at 640x480 with FSAA on (either 2x or 4x). With the new drivers it now locks on initiating Glide whatever the setting or resolution. In D3D the performance is sub my old V2 SLI. I have always run the game at 1024x768 in Glide with very good framerates. I have friends running this game at 1600x1200 at 60fps on an identical CPU to mine using a GeForce2. However, on average I can't get above 25fps at any resolutions (the fps seems unaffected by the resolution and struggles to get above 15 in combat situations). Also in D3D there is a thin horizontal white line across the screen 3/4 of the way down. Whenever I get a few aircraft in view (no matter how distant the fps plummets). From what I have seen SDOE uses a custom Glide2x.dll (is this true)? Could this be where the problem lies? And if so, would RC Sim and any future products from Crosswinds have similarly broken Glide implementation on the V4 / 5 / 6 range of 3dfx cards? Apart from a minor problem with Grand Prix Legends the card is a joy but as SDOE is still my sim of choice I feel I've got a poor return for my £250. I remember a few weeks back you were trying to get your hands on a V5 to look into the issue - did you have any luck / is there any chance of a fix / work around in the near future please? ------------------ Yardstick painted this
IP: Logged |
Michael Harrison General
|
posted 07-27- 06:25 AM
What version of FS did you try this on?We've tried our latest code on the V5 and it worked fine until we loaded the latest beta voodoo drivers. At that point FSAA went to hell, but then mysteriously cleared up a day later (by itself. quite scary). IP: Logged |
VDU Cadet
|
posted 07-27- 06:52 AM
As far as I know (MH correct me if I'm wrong) FS does not use any "special" glide2x DLL. Make sure you do not have any glide2x.dll other than the one that came with your latest driver.
IP: Logged |
Michael Harrison General
|
posted 07-27- 07:18 AM
That's correct. We use whatever glide2x.dll you happen to have on your system.Someone may have confused our ren_glide.dll or the older version of the *renderer* with the 3dfx glide dll. They aren't the same. IP: Logged |
Yardstick Pilot
|
posted 07-27- 07:33 AM
I'm using the SDOE v1.5 executable as I only really play on-line. I will try the latest patch and see if this helps.Yes I may have mistaken 'ren_glide.dll' for a custom 'glide2x.dll'. Thanks as always for the help. I will report back on my experiences. ------------------ Yardstick painted this
IP: Logged |
Geodude Pilot
|
posted 07-27- 01:15 PM
Hey guys - I posted a message with no response a day or two ago on this in the Help/FAQ section...can you take a look? The bottom line is that I was wondering if anyone could implement a quick fix...maybe in that dll file, or something else...Also...has anyone tried running SDOE in Glide using the "Single-Chip" mode (in the anti-aliasing properties tab, I believe)? I know some games work better in that mode (due to the removal of the SLI-like operation required with two chips). Geodude IP: Logged |
Yardstick Pilot
|
posted 07-27- 04:11 PM
OK I tried the beta build 76 and Glide still locks up the system on initiating a mission requiring a cold re-boot. It doesn't matter what resolution I use or FSAA mode.D3D does work but is chock full of graphic anomalies: instruments appear and disappear, the aircraft shadow actually overlays the aircraft (looks very odd), distant terrain textures warp into a multicoloured shimmering mess (giving an effect like the northern lights. Additionally the AI either refuses to take off or does donuts on the runway and some of the engine sounds have done AWOL. Finally the framerate is still appalling (approx 50% of my V2 SLI in Glide) and doesn't seem to alter even if the resolution is turned right down. Oh the reason I though that SDOE used a custom glide render was that there is a file called SDGlide.dll in my root directory. What does that do pls? ------------------ Yardstick painted this [This message has been edited by Yardstick (edited 07-27-2000).] IP: Logged |
Maury Markowitz Pilot
|
posted 07-27- 08:10 PM
quote: Originally posted by Yardstick: D3D does work but is chock full of graphic anomalies:
Hey Yard, I get all of these effects too, on my TNT2. I think these are "generic" bugs in the beta, not anything to do with your card. Maury
IP: Logged |
ReaperMan Pilot
|
posted 07-27- 11:42 PM
Yardy,Try beta build 65. Hopefully that will clear up some graphical glitches. ------------------ -=TheReaper=- IP: Logged |
Michael Harrison General
|
posted 07-28- 06:09 AM
Ok, it turns out that even here, there are some problems.Chad did some additional testing yesterday with our current codebase and found that the engine only works in a few resolutions, with FSAA turned on (640x - 800x I believe). so... This means that I'll be looking at the problem fairly soon just to get RCSim shipped. Which in turn means the fix will get rolled back into FS after RC ships.
IP: Logged |
Yardstick Pilot
|
posted 07-28- 08:30 AM
Michael, that's exactly what I found with the drivers that shipped with the card, Glide would only work at 64x480 with FSAA enabled. However if you try the latest drivers released last Friday, Glide locks the game up completely before the loading screen comes up no matter what the res or FSAA setting. Good to here you're looking into it  ------------------ Yardstick painted this IP: Logged |
Tailslide Pilot
|
posted 07-28- 08:37 AM
Yard, I see the same on my machine  [This message has been edited by Tailslide (edited 07-28-2000).] IP: Logged |
ArthurQ Pilot
|
posted 07-28- 05:37 PM
Well, I had given up on using Glide in SDOE after trying it with my new Voodoo 5500 card and getting the same results that Yardstick has been talking about. I couldn't even get it running properly in 640X480. I'd get these nasty wide black lines all over the place. But just now I went back and tried Glide again and it was running great with 4 Sample antialiasing in 800X600!! I triple checked to make sure I wasn't in D3D and that antialiasing was really selected. I also had meant to try 640X480 at first but apparently miss "clicked" and stayed at 800X600. Man am I surprised. Can't figure it out. Looks great-accept for the usual thin line of "colorful banding" I see at the bottom of the screen ( less than 1/16 of an inch on my 17 inch monitor). Most of my flight sims are showing some sort of banding in Glide with 4 Sample antialiasing at the edge of the screen.D3D has no strange things happening with it though.( Odd since Glide is supposed to be the Voodoo's "thing"). I'll have to see if I can figure out what I've changed in my 3dfx tools that has made SDOE work now. I did print out a Voodoo4/5 tweak guide that I found at www.3dspotlight.net/tweaks/voodoo5/ and I followed alot of the author's tweaks in my 3dfx tools. Maybe that has something to do with it working all of a sudden? I also haven't installed the latest drivers but I'm still using the drivers that came with the CD.AQ [This message has been edited by ArthurQ (edited 07-28-2000).] [This message has been edited by ArthurQ (edited 07-28-2000).] IP: Logged |
Geodude Pilot
|
posted 07-28- 06:41 PM
Michael,Thanks for looking into this...you can always count on a fellow Irishman! Geo (Pat) IP: Logged |
puffman_EAF92 Cadet
|
posted 07-28- 11:43 PM
Gents I have a voodoo 3 2000 and have run the latest drivers from 3dfx gamers.com , these are very similar to the v5 drivers and in fact use the v5 tools , I also have problems with the glide locking up SDOE and have to reboot every time , it must be down to drivers or the tools that are there!IP: Logged |