Page 9 of 9 FirstFirst ... 789
Results 321 to 343 of 343

Thread: Jedi Knight issues

  1. #321
    I don't

    I know such thing exists, but not for 3do files. IIRC JKE models have auto-generated LODs, I'm assuming MotSE doesn't?

  2. #322
    I miss the injector.....

  3. #323

    NIKVMVS-REX-TODOA

    Posts
    16,928
    Yeah, I think JKE had LOD stuff in the models... but since I never messed around with LODs or mipmaps, I really don't know how to tackle this problem aside from the cheap "hey, is there an automated tool for this LOL" ideas :p

    Shame!

  4. #324
    Okay, so I managed to run the injector with the Intel driver by setting a MESA_GL_VERSION_OVERRIDE environment variable to anything higher than 3.3. However, this is what it looked like:

    Click image for larger version. 

Name:	Captura de tela de 2019-04-12 19-21-10.jpg 
Views:	5 
Size:	62.0 KB 
ID:	28459
    Click image for larger version. 

Name:	Captura de tela de 2019-04-12 19-22-12.jpg 
Views:	4 
Size:	30.3 KB 
ID:	28460

    This is what appeared on the console, repeated a bunch of times
    Code:
    Mesa: User error: GL_INVALID_OPERATION in glUseProgram(program 9 not linked)
    Mesa: User error: GL_INVALID_OPERATION in glUniform1("fbuf_dimensions"@1 has 2 components, not 1)
    Mesa: 1 similar GL_INVALID_OPERATION errors
    Mesa: User error: GL_INVALID_OPERATION in glUniform(location=3)
    Mesa: 5 similar GL_INVALID_OPERATION errors
    As for jkgm.log... well...

    [edit]

    Code:
    opengl_state.cpp|20|error> Failed to compile jkgm/shaders/post_to_srgb.frag: 0:23(24): error: sampler arrays indexed with non-constant expressions are forbidden in GLSL 1.30 and later
    opengl_state.cpp|40|error> Failed to link program post_to_srgb: error: linking with uncompiled/unspecialized shader
    this was the output of $ glxinfo | grep OpenGL
    Code:
    OpenGL vendor string: Intel Open Source Technology Center
    OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 610 (Kaby Lake GT1) 
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel (git-8f06559 2019-04-11 bionic-oibaf-ppa)
    OpenGL core profile shading language version string: 4.50
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.0-devel (git-8f06559 2019-04-11 bionic-oibaf-ppa)
    OpenGL shading language version string: 4.50
    OpenGL context flags: (none)
    OpenGL profile mask: compatibility profile
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.0-devel (git-8f06559 2019-04-11 bionic-oibaf-ppa)
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:

    [edit2]
    Tried setting MESA_GLSL_VERSION_OVERRIDE=120. Instead of blurry, screen was now completely white. This is what appeared on jkgm.log:
    Code:
    opengl_state.cpp|40|error> Failed to link program menu: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program game_opaque_pass: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program game_post_ssao: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program game_post_opaque_composite: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program game_transparency_pass: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program post_gauss3: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program post_gauss7: error: vertex shader lacks `main'
    opengl_state.cpp|40|error> Failed to link program post_low_pass: error: vertex shader lacks `main'
    opengl_state.cpp|20|error> Failed to compile jkgm/shaders/post_to_srgb.frag: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, 3.00 ES, 3.10 ES, and 3.20 ES
    opengl_state.cpp|40|error> Failed to link program post_to_srgb: error: linking with uncompiled/unspecialized shader
    and $ glxinfo | grep OpenGL...
    Code:
    OpenGL vendor string: Intel Open Source Technology Center
    OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 610 (Kaby Lake GT1) 
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel (git-8f06559 2019-04-11 bionic-oibaf-ppa)
    OpenGL core profile shading language version string: 1.20
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.0-devel (git-8f06559 2019-04-11 bionic-oibaf-ppa)
    OpenGL shading language version string: 1.20
    OpenGL context flags: (none)
    OpenGL profile mask: compatibility profile
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.1.0-devel (git-8f06559 2019-04-11 bionic-oibaf-ppa)
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
    OpenGL ES profile extensions:
    Last edited by SMLiberator; 04-12-2019 at 08:29 PM.

  5. #325
    Fixed it!
    Click image for larger version. 

Name:	Captura de tela de 2019-04-12 23-41-37.jpg 
Views:	5 
Size:	69.5 KB 
ID:	28463

    Just had to change the version in post_to_srgb.frag to 450 (MESA_GL_VERSION_OVERRIDE is set to 4.5). Framerate is absolutely horrid thanks to the terrible video card, but at least I can see where I'm going with materials.


    So yeah, turns out you CAN run the injector in Wine with Intel graphics with some tweaking. Nice.

  6. #326

    NIKVMVS-REX-TODOA

    Posts
    16,928
    That's pretty cool, given the circumstances!

    Also, I should get around to playing through JK and MotS with the current JKGfxmod + JK/MOTSGFX2019 set-up (mainly to confirm that you can play through the main campaigns of those games with the new stuff), because in some levels there still are some odd crashes involved if (some of) the injected textures are active - Elmo's The Lost Mercenary for one crashes at a specific part if there are injected textures under jkgm\materials (didn't test enough to figure out which textures caused the crashing, I should get around to that at some point).

  7. #327

    NIKVMVS-REX-TODOA

    Posts
    16,928
    Hm. Just tried to debug The Lost Mercenary again and actually got rid of that particular crash by temporarily removing the injected texture pack from T-O:DOA 2 from jkgm\materials - so JKNUP and JKGFX2019 weren't the cause of the crash after all.

    I guess in theory I could check which (one) of T-O:DOA 2's injected textures caused the crash, but eh.
    Last edited by Nikumubeki; 04-13-2019 at 08:47 AM.

  8. #328

    NIKVMVS-REX-TODOA

    Posts
    16,928
    That said, I did discover an interesting translucency issue with one of the 3DOs/surfaces used in that level - the texture appears properly translucent from certain angles (and when you jump at a certain position), but appears buggy otherwise:

    Click image for larger version. 

Name:	jk 2019-04-13 16-42-34-87.jpg 
Views:	2 
Size:	199.9 KB 
ID:	28464

    Click image for larger version. 

Name:	jk 2019-04-13 16-42-39-44.jpg 
Views:	2 
Size:	169.8 KB 
ID:	28465

    Click image for larger version. 

Name:	jk 2019-04-13 16-42-45-27.jpg 
Views:	2 
Size:	182.2 KB 
ID:	28466

    Click image for larger version. 

Name:	jk 2019-04-13 16-42-47-37.jpg 
Views:	2 
Size:	198.2 KB 
ID:	28467

    (Once again getting BSP hole vibes from it - I swear, one of these days a BSP error or something like it will actually kill me)

  9. #329
    That might actually be a JK limit and not an injector issue. JK can only display up to 32 transluscent level surfaces at the same time, so that's probably that.

  10. #330

    NIKVMVS-REX-TODOA

    Posts
    16,928
    Quote Originally Posted by SMLiberator View Post
    That might actually be a JK limit and not an injector issue. JK can only display up to 32 transluscent level surfaces at the same time, so that's probably that.
    Ah, yes. Sort of convinced myself that the issue had been fully sidestepped by the injector. >_>

  11. #331
    Admiral of Awesome
    Posts
    17,648
    I've never even heard of such a limit. ****ing why?


    Edit: Let me guess. In software mode, they draw all of the transparent level surfaces in a second pass. So they accumulate the first 16 they see in a static array and drop the rest on the floor. Cache? What's cache?
    Last edited by Jon`C; 04-13-2019 at 11:14 AM.

  12. #332

    NIKVMVS-REX-TODOA

    Posts
    16,928
    Quote Originally Posted by Jon`C View Post
    I've never even heard of such a limit. ****ing why?
    I remember asking ZeqMacaw in 2009 about it, like "why does JK do this with translucent surfaces?" and his response basically was "JK can only show a certain amount of translucent surfaces on the screen, and what's wrong with you why did you have to ask this question :S"

    Come to think of it, Zeq was one of the few people I actually hated. Hrr.

  13. #333

    NIKVMVS-REX-TODOA

    Posts
    16,928
    That said, I did make a tiny little fix that should let one play TODOA TC SP with JkGfxMod sabers (thus skipping JK13 altogether, and just going with the January 2008 JKUP), which is kind of cool.

    However, I did notice a FreeColorEffect related issue (maybe the same one SMLiberator mentioned before), when the saber is being activated at the same time when the FreeColorEffect is ... in effect:

    Click image for larger version. 

Name:	act1.jpg 
Views:	42 
Size:	189.1 KB 
ID:	28473

    Click image for larger version. 

Name:	acti2.jpg 
Views:	40 
Size:	298.6 KB 
ID:	28474

    Also, looking at the comments JKGFX2019 has received, an OGG injector would probably be very helpful.

  14. #334
    Admiral of Awesome
    Posts
    17,648
    Just uploaded jkgfxmod v0.0.10.

    This roughly doubles framerates. Apparently a minor tweak I pushed a few days ago wasn't so minor. :shrug:

  15. #335
    Quote Originally Posted by Jon`C View Post
    Just uploaded jkgfxmod v0.0.10.

    This roughly doubles framerates. Apparently a minor tweak I pushed a few days ago wasn't so minor. :shrug:
    Nice, I gotta test this. Maybe now my poor little laptop won't have to struggle so much.
    Sorry for the lousy German

  16. #336

  17. #337

    NIKVMVS-REX-TODOA

    Posts
    16,928
    Very nice!

    However, it didn't fix the "Elmo's The Lost Mercenary crash", which I seem to have pin-pointed to this one texture with an FGR-made displacement map. I should get around to the JKGM.log environment variable at some point.

  18. #338
    Okay, so I'm getting playable framerates (around 30, but still playable) with the Intel card on Wine. Great.

    Out of curiosity: could you add some more variables to jkgm.json (like "enable_bloom" or "enable_materials") to further tweak graphics settings? Maybe that could also help with FPS in weaker GPUs.

  19. #339
    Admiral of Awesome
    Posts
    17,648
    That’s a good idea in general. Can you elaborate on the use case for “enable materials”, please? You can already disable materials (in a way) by deleting the materials directories.

  20. #340
    Admiral of Awesome
    Posts
    17,648
    Quote Originally Posted by Nikumubeki View Post
    Very nice!

    However, it didn't fix the "Elmo's The Lost Mercenary crash", which I seem to have pin-pointed to this one texture with an FGR-made displacement map. I should get around to the JKGM.log environment variable at some point.
    I would guess it’s a GPU crash really, which isn’t an excuse (jkgm shaders shouldn’t do that) but unless I know what’s going wrong I can’t possibly fix it.

    Does it still happen if you turn off parallax in the config?

  21. #341
    Quote Originally Posted by Jon`C View Post
    Can you elaborate on the use case for “enable materials”, please? You can already disable materials (in a way) by deleting the materials directories.
    Well... that's pretty much all that I had in mind, yes. Just for disabling materials without having to move directories around. Also, I think it's nice to have extra options available (regardless of how useful they actually are). You could take pointless variables a step further and throw in "enable_emissive" or something of that kind (maybe these could be useful for debugging? who knows).

  22. #342
    Admiral of Awesome
    Posts
    17,648
    Smells like shader permutations.

  23. #343

    NIKVMVS-REX-TODOA

    Posts
    16,928
    Does it still happen if you turn off parallax in the config?
    Nope, which actually led me to discover the texture that causes the crash.

    No idea what directly causes the crash itself (should env-var it at some point), but basically the displacement texture creates a pipe shape. But in Elmo's level, the 3DO using that texture already is pipe-shaped, which may have created some kind of a pipeception that JK couldn't handle.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •