Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: CuBes on January 04, 2008, 01:06:33 pm
-
This problem concerns both FS2 and FS1. My computer has trouble playing the game without graphics acceleration, but when I enable Direct3D, I have a strange bug, where certain parts of ships become invisible, revealing the texture on the opposite side. It looks the same as if you were wandering through the ship due to taking advantage of a clipping bug. This OpenGL, or possibly Direct3D, glitch mainly affects large vessels, but I have seen it appear on freighters, cruisers, and even parts of fighters. It's hard to fully describe the bug; instead, I have taken screenshots and posted them on a webspace, at http://infohost.nmt.edu/~dwood/freespace/OpenGLbug/openGL.htm (http://infohost.nmt.edu/~dwood/freespace/OpenGLbug/openGL.htm) . Needless to say, its strange and at times, difficult playing like this. If someone can offer a solution, or even identify the problem, I would appreciate it.
Attatched is DirectX Diagnostic's system report on my PC.
[attachment deleted by ninja]
-
Are these the retail FS1 and FS2 or is this FSO? Because, if you're playing FSO, just stick to OpenGL to avoid graphical problems. If you're playing retail FS2, switch to FSO.
-
Yes they are retail. The problem exists when I switch to OpenGL, then I have model rendering issues. When I am not in OpenGL mode, I can't always see the screen (it sometimes remains black).
Also, I had this problem before upgrading my motherboard, CPU, and graphics card, and before I bought a new harddrive and a legitimate version of both games.
If FSO extends functionality to FS1, and I can use it to overcome this graphical issue, then it would be most helpful, but as I understand it, FSO is only coded for FS2.
-
FSO is indeed derived from FS2's engine, but certain brave people have done the FSPort, which ports the FS1 campaign to FSO. So you can, in a way, play FS1 with FSO. And don't forget all the fantastic graphical enhancements the whole Source Code Project has. Getting FSO is also easy. There's a link to Turey's FSO Installer in my signature, but you might want to consult these instructions (http://www.hard-light.net/forums/index.php/topic,47640.0.html) since you already have FS2. That'll save you some download time.
-
I appreciate the solution, but I hesitate to converting all of my Freespace data for FSO. Is this the best, or possibly the only solution to my problem? I had considered it before, but I didn't want to follow through with it. Most people I have asked in the past have been unable to help with the OpenGL problem I have, not knowing of its existence. Have you, or anyone else, encountered the OpenGL bug I have described, and if so, were there any known fixes or workarounds?
-
This problem is totally new to me, so I can't help you solve it. Other than suggesting FSO. You can, of course, take a backup of your C:\...\freespace\data\players folder. This way, if you mess up with FSO, you can uninstall it completely, reinstall FS2 and copy the said folder back to its place. FS1 is not affected in any way if you choose to install FSO, which I once again recommend.
-
CuBes probably won't be able to play FSO. Not with an 8500.
-
Point there. At least not with the mediavps. But still he could give it a try. Yoda might say 'There is no try', but I say go for it. You only live once, unless proven otherwise.
-
A Geforce 8500? Of course he can play FSO with the media VPs, he'll be able to play them with everything enabled as well. I have a Radeon X1600 (comparable to the Geforce 7600), and I can turn everything on. Can't help you with your problem though, try a driver update?
-
Card name: ALL-IN-WONDER RADEON 8500DV
Manufacturer: ATI Technologies Inc.
Chip type: Radeon 8500 (BB)
DAC type: Internal DAC(350MHz)
Device Key: Enum\PCI\VEN_1002&DEV_4242&SUBSYS_02AA1002&REV_00
Display Memory: 64.0 MB
I mean, eww. With that graphical memory his rig is sure to clog up with all the goodies enabled. Besides, All-in-Wonders are generally not meant for heavy gaming usage.
On a side note, I have a Mobility X1600 and I also am able to turn all the features on, though numerous simultaneous ships, excessive nebula usage and, now with 3.6.10, asteroid fields make my rig cough blood.
-
Oh, a Radeon 8500, thought you meant a Geforce 8500. Yea, with that you're probably not gonna be able to run much mate :p
-
If I upgrade my graphics drivers, my TV playback won't work... strange bug on ATI's part. In the mean time I suppose I can give FSO a shot. On that note, I use certain clipping bugs whenever possible. Does FSO fix these? They are: A warp in bug, where a player can go inside of a capitol ship that is warping in, and a regular clipping glitch, where a player can find a sharp angle in the model of a ship and pass through it to the inside of a ship. I might have to try for myself, if you don't know what I mean, but all retail Freespace games have these bugs. My guide, http://www.gamefaqs.com/computer/doswin/file/197099/20864 (http://www.gamefaqs.com/computer/doswin/file/197099/20864), explains the bug in more detail.
Also, is silent threat ported to FSO?
-
Also, is silent threat ported to FSO?
Yes, comes with the FSPort. And it actually works properly.
Edit: Not to mention that Silent Threat: Reborn is soon (or 'soon and soon') ready.
-
Radeon 8500 is capable of running FSO pretty well. With similar detail settings it probably fares better with FSO than it does with the retail.
Of course, when you start enabling the more advanced gfx options it suffocates at some point (stay away from env mapping especially).
-
I fixed the FS2 problem somehow, but it still persists in FS1.
-
What I'm finding really strange is that FS1 and FS2 don't actually run in OpenGL.
What is the name of the program you are running? FReespace.exe\Freespace2.exe or Launcher.exe?
-
I run the FS1 Launcher, the setup is set to Direct3D (not openGL specifically), then hit the play button, and it launches the game.
-
Just to let you know, the most common gripe about the FSPort is that the AI changed significantly between FS1 and FS2, and I don't know if it's easy to get the FS1 AI behaviour into FSPort yet. If you're a really big stickler for that, you'll notice the difference. I consider it minor though.