Hard Light Productions Forums

Hosted Projects - Standalone => Diaspora => Diaspora Tech Help => Topic started by: karajorma on July 12, 2012, 01:46:06 am

Title: Known Issues
Post by: karajorma on July 12, 2012, 01:46:06 am

Windows

Joysticks

Several users have been reporting issues with joystick detection in-game. To fix it, try this, go to Control Panel -> Game Controllers. Select "Advanced" and set your controller as the preferred device.

You should also check that your joystick has been successfully by the launcher on the Basic Settings tab.


All Platforms

Diaspora Mission Editor

If #Weak weapons are enabled in player loadout it will crash your mission. These weapons are meant for AI use, not players.
Note: Fixed pending patch 1

Multiplayer

Cylon Raiders and Advanced Raiders will currently crash the game for the player. (also will crash first person view from a raider in singleplayer)
Cylon Heavy Raiders are playable.
Note: Fixed pending patch 1

Title: Re: Known Issues
Post by: newman on September 24, 2012, 10:04:43 am

I'd like to add this here rather than starting a new thread.

- before reporting a graphics issue, please make sure you have the latest graphics card drivers installed. If you don't, update them and check if the issue is resolved before reporting a problem.

- if your issue is persistent, when posting about it please include your configuration info: CPU, amount of RAM, graphics card, and OS version at least.

Title: Re: Known Issues
Post by: Avalean on October 23, 2013, 04:18:49 pm

Just downloaded the game and patch for windows7.
Set the launcher for Run as Standalone Server
Now that the server is running how do I enter the server I created to play with my mates?

I mean I select to log into the FS2net2 server set, there I select the mod I am using and I see the server but I see no where to click that will allow me ot enter the server nor to place in the set password for server entry.

So I can see the server running in FS2net2 but see no way of entering the game from that point.

Title: Re: Known Issues
Post by: Iago Santaniello on December 28, 2013, 12:58:18 pm

I have just built the game for Linux, and I started it up. However, it crashed when I selected my pilot. If I use the launcher it says: Freespace 2 open exited with a status of -1
If I use the terminal it says:

ATTENTION: default value of option force_s3tc_enable overridden by environment.
Segmentation fault (core dumped)

Title: Re: Known Issues
Post by: Echelon9 on December 28, 2013, 05:19:07 pm

Which Linux distribution have you used (I.e. Ubuntu 12.04)?

Title: Re: Known Issues
Post by: niffiwan on December 28, 2013, 05:54:50 pm

Sounds somewhat similar to the issues reported here: http://www.hard-light.net/forums/index.php?topic=85985.20

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

Also - the log will tell us, but do you have an Intel video card?

Title: Re: Known Issues
Post by: Iago Santaniello on December 29, 2013, 02:51:51 am

I use Ubuntu 13.10. And I didn't find the log anywhere after following the steps, and it still crashes. And yes, I use an intel i7 quad core CPU.

Title: Re: Known Issues
Post by: jg18 on December 29, 2013, 03:19:39 am

Did you re-run autogen.sh with the --enable-debug option?

Code: [Select]

./autogen.sh --enable-debug

and then re-run make?

Code: [Select]

make clean && make


Title: Re: Known Issues
Post by: Iago Santaniello on December 29, 2013, 03:55:03 am

I tried, still crashes

Title: Re: Known Issues
Post by: Iago Santaniello on December 29, 2013, 04:27:40 am

I have traced the coredump (what made it crash):

Core was generated by `./fs2_open_diaspora'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007feb7d91ed9e in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(gdb) bt full
#0  0x00007feb7d91ed9e in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
No symbol table info available.
#1  0x00007feb7d40b6a6 in _mesa_ReadnPixelsARB ()
   from /usr/lib/x86_64-linux-gnu/libdricore9.2.1.so.1
No symbol table info available.
#2  0x00007feb7d40b89a in _mesa_ReadPixels ()
   from /usr/lib/x86_64-linux-gnu/libdricore9.2.1.so.1
No symbol table info available.
#3  0x00000000004dd065 in gr_opengl_save_screen() ()
No symbol table info available.
#4  0x0000000000716117 in popup_do(popup_info*, int) ()
No symbol table info available.
#5  0x00000000007168a4 in popup(int, int, ...) ()
No symbol table info available.
#6  0x00000000005a9cd9 in player_tips_popup() ()
No symbol table info available.
#7  0x0000000000599d84 in main_hall_do(float) ()
No symbol table info available.
#8  0x00000000004c8837 in gameseq_process_events() ()
No symbol table info available.
#9  0x0000000000441fb2 in game_main(char*) ()
No symbol table info available.
#10 0x000000000040b31d in main ()
No symbol table info available.

Title: Re: Known Issues
Post by: Echelon9 on December 29, 2013, 05:43:09 pm

Although support for Intel integrated graphics has been patchy at best, there has been a recent influx of crash reports on Ubuntu 13.10 (64bit) with this hardware.

Investigating to see if there is a recent change in the underlying platform which can be worked around.

Please follow Mantis #2988 (http://scp.indiegames.us/mantis/view.php?id=2988) for updates.

Title: Re: Known Issues
Post by: niffiwan on December 29, 2013, 07:41:29 pm

I've added a command line flag to disable the use Pixel Buffer objects.  I suspect that there's a bug in the Intel Linux drivers, or they aren't quite following the OpenGL specification.

Anyway: could you please try compiling & running this code to see if that works around the issue?
https://github.com/niffiwan/fs2open.github.com/commits/mantis2988

You will need to set "-disable_pbo" on the command line, or via the launcher (Advanced -> Troubleshooting -> "Disable OpenGL Pixel Buffer Objects")

edit: the workaround has been committed to trunk in r10268.

Title: Re: Known Issues
Post by: Akaimahomiru on June 01, 2014, 11:58:27 am

The game was playing fine till last night, I get this error constantly now after intial UI bootup, I click on either Briefing and fs2 freezes or Tech Data and I get this:
Submodel <Seata> in model <Col_Viper_Mk7.pof> has a radius <= 0.1f

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.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>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

and then fs2 freezes and after selecting yes to debug, and i have to close program

[attachment deleted by an evil time traveler]

Title: Re: Known Issues
Post by: niffiwan on June 01, 2014, 04:15:54 pm

The message is a warning.  You can safely ignore that one, so press "No" to continue (instead of "Yes" to debug).