Author Topic: Just Another Troubleshooting Thread  (Read 75856 times)

0 Members and 1 Guest are viewing this topic.

Re: Just Another Troubleshooting Thread
No, they weren't cut off, installed 2.21 and 2.22 files to the same folder. Now it crashes even at the loading screen. Log attached

[attachment eaten by a Shivan]

 
Re: Just Another Troubleshooting Thread
According to the log neither JAD nor the MVPs are loaded.

 
Re: Just Another Troubleshooting Thread
From terminal
Code: [Select]
./fs2_open_19_0_0_RC2_x64.AppImage -mod JAD-2.23
FSO is running in legacy config mode. Please either update your launcher or copy the configuration and pilot files to '/home/oliver/.local/share/HardLightProductions/FreeSpaceOpen/' for better future compatibility.
Aborted (core dumped)
Obviously, it doesn't work with wxlauncher 0.9

 
Re: Just Another Troubleshooting Thread
Debug build from terminal
Code: [Select]
./fs2_open_19_0_0_RC2_x64-FASTDBG.AppImage -mod JAD-2.23
FSO is running in legacy config mode. Please either update your launcher or copy the configuration and pilot files to '/home/oliver/.local/share/HardLightProductions/FreeSpaceOpen/' for better future compatibility.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 3 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 4 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 5 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 7 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 8 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use VIDEO memory as the source for buffer object operations.
Trace/breakpoint trap (core dumped)

 
Re: Just Another Troubleshooting Thread
Are you using Knossos in combination with a wxLauncher?

 
Re: Just Another Troubleshooting Thread
Trying to manually launch with -mod JAD 2.23 won't work, you need MVPs too(and JAD 2.21 and 2.22 if the .vps aren't in the same folder). So your cmdline needs to be at least -mod JAD 2.23,MediaVPS_40.

Your log again shows:
FreeSpace 2 Open version: 19.0.0.RC2
Passed cmdline options:
  <none>

[19:31] <MatthTheGeek> you all high up on your mointain looking down at everyone who doesn't beam everything on insane blindfolded

  
Re: Just Another Troubleshooting Thread
Code: [Select]
/home/oliver/Freespace2/fs2_open_19_0_0_RC2_x64-FASTDBG.AppImage -mod JAD-2.23,MediaVPs_40 -nomotiondebris -3dshockwave -post_process -soft_particles -fxaa -smaa -fb_explosions -fb_thrusters -enable_shadows -dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -ship_choice_3d -weapon_choice_3d -3dwarp -warp_flash -mipmap -missile_lighting -snd_preload -no_glsl -spec -glow -env -normalThis is how the commandline looks in wxlauncher

 
Re: Just Another Troubleshooting Thread
Well clearly your launcher isn't passing those flags onto the game itself since it's launching with no commandline parameters. You said you use wxL 0.9, I'm pretty sure that one doesn't have proper SDL support which has been in master since 3.8 so you need to switch to a newer version of wxL or use Knossos.
Or if you want to you could write the commandline manually but that's a huge PITA.
[19:31] <MatthTheGeek> you all high up on your mointain looking down at everyone who doesn't beam everything on insane blindfolded

 
Re: Just Another Troubleshooting Thread
If wxLauncher doesn't work, maybe just try the 5.5g one. Editing the cfg file isn't that hard though (atleast when you have an idea what you're doing).

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Just Another Troubleshooting Thread
5.5g is Windows only & won't run on Linux (unless you want to try Wine but that's just adding needless complexity)

Code: [Select]
/home/oliver/Freespace2/fs2_open_19_0_0_RC2_x64-FASTDBG.AppImage -mod JAD-2.23,MediaVPs_40 -nomotiondebris -3dshockwave -post_process -soft_particles -fxaa -smaa -fb_explosions -fb_thrusters -enable_shadows -dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -ship_choice_3d -weapon_choice_3d -3dwarp -warp_flash -mipmap -missile_lighting -snd_preload -no_glsl -spec -glow -env -normalThis is how the commandline looks in wxlauncher

What happens if you run that command line from a terminal, when you've cd'd to the correct FS2 directory? e.g. from a knossos install it's probably called "FS2", and it'll have all the retail VPs plus the mod dirs in it.
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Just Another Troubleshooting Thread
Code: [Select]
FSO is running in legacy config mode. Please either update your launcher or copy the configuration and pilot files to '/home/oliver/.local/share/HardLightProductions/FreeSpaceOpen/' for better future compatibility.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL TFSO is running in legacy config mode. Please either update your launcher or copy the configuration and pilot files to '/home/oliver/.local/share/HardLightProductions/FreeSpaceOpen/' for better future compatibility.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 2 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 3 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 4 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 5 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 7 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 8 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 10 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 11 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING_ARB (0), and GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) stored in VIDEO memory has been updated.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING_ARB (0), and GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use VIDEO memory as the source for buffer object operations.

ype:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 3 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 4 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 5 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 7 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 8 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 10 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 11 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING_ARB (0), and GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) stored in VIDEO memory has been updated.
OpenGL Debug: Source:OpenGL Type:Other ID:131185 Severity:UnknownMessage:Buffer detailed info: Buffer object 9 (bound to GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING_ARB (0), and GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use VIDEO memory as the source for buffer object operations.

Log attached

[attachment eaten by a Shivan]

 
Re: Just Another Troubleshooting Thread
1. Okay, why not just run it from Knossos, then? Knossos based FSO install just copies a couple files from your FS2 install and both Knossos and wxLauncher based installations can coexist.

2.
Code: [Select]
  OpenGL Vendor    : NVIDIA Corporation
  OpenGL Renderer  : GeForce 315/PCIe/SSE2
  OpenGL Version   : 3.3.0 NVIDIA 340.107
Huh. If I'm right, this graphics card is actually slower than most Intel integrated graphic chips. Also I think it has got 512MB of VRAM which I'm pretty sure won't be enough... How in the world did you manage to play other campaigns on it, especially with these flags?

Also I'm pretty sure -no_glsl doesn't work for quite a bit now.
Mito [PL] - Today at 8:52 PM
I was supposed to make a short presentation about basics of optical fibers and here I am, listening to Eurobeat while reading about quantum cryptography.

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
JAD is particularly graphics and memory intensive (lots of ships, effects, and not to mention animated png sprites) so it wouldn't surprise me that your system may not have the ability to play it if that's the video card its trying to run on. Does playing just with the mediavps work?

 
Re: Just Another Troubleshooting Thread
JAD is particularly graphics and memory intensive (lots of ships, effects, and not to mention animated png sprites) so it wouldn't surprise me that your system may not have the ability to play it if that's the video card its trying to run on. Does playing just with the mediavps work?

Launching the game probably isn't the problem, just what comes afterwards is...

 
Re: Just Another Troubleshooting Thread
Even Blueplanet works with the MediaVPs 4.0, however, Knossos cannot run on 16.04, the repository works with 17.04 onwards

 
Re: Just Another Troubleshooting Thread
If you managed to get BP with MVP-4-0 to work with that, couldn't you just drop the files into the BP folder?

 

Offline Axem

  • Moderator
  • 211
Re: Just Another Troubleshooting Thread
I have only one other shot in the dark.

Can you make the directory
Code: [Select]
/home/oliver/Freespace2/JAD-2.23/data/tables
And put the attached table file in there?

There was an issue with WoD not working because older AMD cards didn't work with TTF fonts. The workaround was telling the game to use just the old style default vf fonts. I can't guarantee everything will look as nice, but it might stop the crashing.

[attachment eaten by a Shivan]

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Just Another Troubleshooting Thread
Given these errors below in the log you could also try removing the '-fxaa' & '-smaa' flags (if fact I'm pretty sure they're not meant to be used together!), and maybe even lowering the resolution a bit? e.g. add -res 1200x900 (or some other value that'll work OK on your monitor, maybe running in a window with the -window flag might also be useful)

I'd also recommend removing these flags, at best they don't do anything, at worst they'll cause issues:
  -mipmap
  -enable_shadows (this really hurts performance on an old video card)
  -spec (doesn't do anything)
  -glow (doesn't do anything)
  -normal (doesn't do anything)
  -env (doesn't do anything)
  -missile_lighting (doesn't do anything)

Also, can you find a more recent version of the nVidia drivers available in Ubuntu repo's? 340.107 is pretty old, I have 390.116 installed (admittedly that's from Mint 19/Ubuntu 18.04)

Code: [Select]
  Initializing SDL video...
Initializing OpenGL graphics device at 1600x1200 with 32-bit color...
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
Could not create OpenGL Context: Could not create GL context: BadMatch (invalid parameter attributes)
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
Could not create OpenGL Context: Could not create GL context: BadValue (integer parameter out of range for operation)
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
Could not create OpenGL Context: Could not create GL context: BadValue (integer parameter out of range for operation)
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
Could not create OpenGL Context: Could not create GL context: BadValue (integer parameter out of range for operation)
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
Could not create OpenGL Context: Could not create GL context: BadValue (integer parameter out of range for operation)
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
Could not create OpenGL Context: Could not create GL context: BadValue (integer parameter out of range for operation)
  Requested SDL Pixel values = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 2
  Actual SDL Video values    = R: 8, G: 8, B: 8, depth: 24, stencil: 8, double-buffer: 1, FSAA: 0
  OpenGL Vendor    : NVIDIA Corporation
  OpenGL Renderer  : GeForce 315/PCIe/SSE2
  OpenGL Version   : 3.3.0 NVIDIA 340.107
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Just Another Troubleshooting Thread
Also, can you find a more recent version of the nVidia drivers available in Ubuntu repo's? 340.107 is pretty old, I have 390.116 installed (admittedly that's from Mint 19/Ubuntu 18.04)
390.116 will not work with GeForce 315. Nvidia dropped support for anything older than GeForce 400 Series in this driver.

 

Offline SL1

  • 26
Re: Just Another Troubleshooting Thread
I keep getting a crash during what I presume is the final boss fight of JAD 2.23.

Spoiler:
It happens a few seconds after Henrietta's core falls to 0 percent hull.

I'm using the Knossos version. Aside from some minor HUD tweaks, I haven't done anything to the files, so I don't know what might be the problem.