Hard Light Productions Forums
Hosted Projects - Standalone => Diaspora => Diaspora Tech Help => Topic started by: Wobble73 on May 10, 2014, 02:54:40 pm
-
I have been trying to run Diaspora on a new laptop but I kept getting strange clipping artifacting going on that made playing impossible! Now when I try to run it my computer justs hangs when I try to go to the briefing. I have attched my debug log. Anyone know what is going on here?
[attachment deleted by an evil time traveler]
-
What do you mean by "clipping artefacting"? Can you get a screenshot of it?
Also, I see that you're using the "-ati_swap" commandline switch, you really do not need it (it was a compatibility hack for really really old ATI chips).
-
I can't get a screenshot now as it no longer runs. It just hangs and then crashes. I picked the ATI swap switch as I am using an AMD Radeon HD8180 and figured it may help.
It seems to work now when I choose the non debug build but I still get the graphical errors but I can't seem to capture a screenshot. When I press the windows key and the prt scr button I get the windows behind the game, not the the game itself?
-
If you're running fullscreen, press "Prt Scr" in game and a screenshot should be created in Diaspora/screenshots (or maybe Diaspora/data/screenshots, I'm on Linux so this is from memory). It'll be called screenXXXX.tga.
If you're using Windows 7 and running in a window there's a neat snipping tool that should also work. Search for "snip" in the start menu.
-
I have tried that and it doesn't seem to work. I am on Windows 8 64bit btw.
EDIT
I have managed to take some screenshots using the "Run in Window" flag, please see attached.
[attachment deleted by an evil time traveler]
-
Try also removing the -img2dds command line flag. It affects texture compression and you shouldn't need it.
You could probably also remove -noenv, your video card should be powerful enough to handle environment mapping.
For Diaspora, the radar is the DRADIS so -orbradar won't have any effect and can probably be removed.
Lastly, you should grab the Diaspora 1.1.1 patch (http://www.hard-light.net/forums/index.php?topic=87443.0) to fix an issue with the last mission in the campaign.
-
I have tried those with still no effect? I have a feeling that my catalyst drivers are to blame, yet I can play BP WiH with no problems? My Windows 8 won't upgrade to 8.1 and updates fail and revert. It's something to do with the registry I believe but hacking that seems very complicated?
Also my Windows is preventing the patch 1.1.1 to run??
-
Hmm. Are your Cataylst drivers up to date? Also, are you running a "BP build" or the executable that came with 1.1.1? The fact that BP runs fine but Diaspora doesn't is quite odd...
-
Still haven't found a solution to this, I have no upgraded to Windows 8.1 and checked my Catalyst drivers are up to date. I am still getting the same effects no matter what graphics options I choose!
-
Bump, does no-one have a solution for me?
-
Run the patch in administrative mode. If that doesn't work, re-download the patch and try in admin mode again.
-
The patch has been applied now, but it still gives me a bad view. It's like it is clipping or something but there is nohing to clip with?
Edit here is the latest debug log
[attachment kidnapped by pirates]
-
Hmm, disable desktop composition in the compatibility settings for the fso exe?
-
Also try removing these command line options - from the thread I think you've tried with some of them off, but I'm not 100% sure you've tried with all of them off. Some of these have been known to cause issues for certain configurations rather than solve them!
-img2dds
-mipmap
-ati_swap
If it still has the clipping issue with them off, create & post a new log, and some more screenshots (since the last ones have been eaten, try uploading them to somewhere like http://imgur.com/ and then link to them, that way they won't be deleted so quickly.
-
Now it won't even play? It exits with an error stating "Freespace 2 exited with a status of -805306369"?
-
That certainly is odd... so... log log log :)
-
Here is my latest debug log.
Advanced settings tab on the launcher now states "Waiting for flaf file to begenerated and parsed"?
[attachment kidnapped by pirates]
-
You've still got -img2dds in your cmdline parameters.
Also, what happens if you run the FSO executable directly, i.e. not from the launcher?
-
Ho do I remove -img2dds from my command line? I assume it is due to some setting being selected in the launcher, but I don't know which one it is related to? Also, I will have to check running from the executable when I return to my home computer, (at work at the moment on my lunch hour).
-
Ah, took me a little while to find that; it's "Compress non-compressed images"
-
Gone back to Diaspora build debug release 1 because the settings flag wouldn't generate or parse for other builds, removed -img2dds and now I get this error
Submodel <Seata> in model <Col_Viper_Mk7.pof> has a radius <= 0.1f
ntdll.dll! NtWaitForSingleObject + 12 bytes
KERNELBASE.dll! WaitForSingleObject + 18 bytes
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 14 bytes
ntdll.dll! RtlInitializeExceptionChain + 132 bytes
ntdll.dll! RtlInitializeExceptionChain + 90 bytes
[\code]
Attached is my new log
[attachment kidnapped by pirates]
-
Is that a fatal error, or just a warning? It almost sounds like the latter - if you hit "No" at the bottom of the message, does the game continue?
If so, this would make it a warning that only appears when you run a debug build - it shouldn't appear when running the standard executable and could be safely ignored if the game otherwise works fine.
-
Yes it was just a debug warning in the end, I advanced through to the game by just clicking on "no" (about six or seven warnings though).
I am still getting the srewy graphics though I'll upload some screenies soon.
(http://i.imgur.com/bGn3ESG.png) (http://imgur.com/bGn3ESG)
(http://i.imgur.com/NTGqWhv.png) (http://imgur.com/NTGqWhv)(http://i.imgur.com/9YyGmMx.png) (http://imgur.com/9YyGmMx)
(http://i.imgur.com/R3IxxKp.png) (http://imgur.com/R3IxxKp)
(http://i.imgur.com/L2aru3Z.png) (http://imgur.com/L2aru3Z)
(http://i.imgur.com/OFyr4Ai.png) (http://imgur.com/OFyr4Ai)
(http://i.imgur.com/d8E015K.png) (http://imgur.com/d8E015K)
(http://i.imgur.com/k8d0cwO.png) (http://imgur.com/k8d0cwO)
(http://i.imgur.com/oYXlDsq.png) (http://imgur.com/oYXlDsq)
(http://i.imgur.com/N4KrtGW.png) (http://imgur.com/N4KrtGW)
-
OK, so I've actually looked up your video card now and found that it's some sort of AMD integrated card? Which means that its not as powerful as I thought. Therefore can you try removing these command line options and see if any of them make a difference:
-soft_particles (Enable soft particles)
-post_process (Enable Post Processing)
-fxaa (Enable FXAA anti-aliasing)
If that doesn't help, then maybe try turning all these off as well.
-no_vsync (Disable vertical sync)
-disable_fbo (Disable OpenGL RenderTargets)
-disable_pbo (Disable OpenGL Pixel Buffer Objects)
-no_glsl (Disable OpenGL Pixel Buffer Objects)
And if that doesn't work try with just -no_glsl enabled.
-
I think I have tried all these (basically I have been through the launcher switching things off and on again). Besides, the chip is powerful enough for it to play Blue Planet on mid/high settings with hardly any lag?
-
True - I had forgotten that. I had just found a review online that unfavourably compared the 8180 with the Intel HD 4000.
And sorry, if that hasn't fixed the issue, and your drivers are up to date, then I'm officially out of ideas :(