Duke4.net Forums: Screen goes black in Polymer renderer under consistent circumstances, R7793 and R7800 - Duke4.net Forums

Jump to content

Hide message Show message
Welcome to the Duke4.net Forums!

Register an account now to get access to all board features. After you've registered and logged in, you'll be able to create topics, post replies, send and receive private messages, disable the viewing of ads and more!

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Screen goes black in Polymer renderer under consistent circumstances, R7793 and R7800

#1

Please note the title says R7793 but I have just tested with R7800 and the same thing occurs. Happens with fresh config files also and does not occur in Polymost or Software modes.

Specs of system:

- Intel Core i7 4770K
- Z87 Chipset
- NVIDIA GeForce GTX 970 (drivers have been updated as part of testing)
- Windows 10 1809.
- EDuke32 64-bit

EDIT: R7743 is the first release on Synthesis this happens to me. Any older release has no problem.



This post has been edited by Mitch Richters: 16 July 2019 - 04:14 AM

0

#2

Yup, i've already reported this when i tried the updated Stopgap::

View PostThe Battlelord, on 29 June 2019 - 06:07 PM, said:



it happens when there are mirrors in the area.The game keep running, indeed the player can move, fire, jump etc... but is pratically impossible to play.If you switch from Polymost to Polymer in front of a mirror, boom, black screen, then, I guess that it could turn back to normal if you switch to Polymost again, but i was unable to do it as everything is black, you should learn the path via keyboard and try, but i don't think that is worth the time :D.



This post has been edited by The Battlelord: 16 July 2019 - 08:42 AM

0

User is offline   Mark 

  • Honored Donor

#3

The mirror issue started somewhere between 7622 and 7750. I'll bisect shortly and find out when it started.
EDIT: 7657 was good. the next public revision 7743 was bad. So the issue is sandwiched in all those unreleased revisions. Unfortunately its a whole lot of them. 7733 and 7736 in the changelog mentions mirrors but for software and polymost. But I suppose the bug could come from many other places.

This post has been edited by Mark: 16 July 2019 - 09:58 AM

0

User is offline   LeoD 

#4

Compile-bisect says that r7736 is the culprit.
2

User is offline   Mark 

  • Honored Donor

#5

Usually I get stuck with doing that after Hendricks provides me with a bunch of compiled versions to test. Thanks a bunch.
0

#6

View PostThe Battlelord, on 16 July 2019 - 08:32 AM, said:

Yup, i've already reported this when i tried the updated Stopgap:: it happens when there are mirrors in the area.The game keep running, indeed the player can move, fire, jump etc... but is pratically impossible to play.If you switch from Polymost to Polymer in front of a mirror, boom, black screen, then, I guess that it could turn back to normal if you switch to Polymost again, but i was unable to do it as everything is black, you should learn the path via keyboard and try, but i don't think that is worth the time :D.

Ah ok, no worries. Apologies, I didn't know it was reported but glad I'm not the only one :)

View PostMark, on 16 July 2019 - 09:44 AM, said:

The mirror issue started somewhere between 7622 and 7750. I'll bisect shortly and find out when it started.EDIT: 7657 was good. the next public revision 7743 was bad. So the issue is sandwiched in all those unreleased revisions. Unfortunately its a whole lot of them. 7733 and 7736 in the changelog mentions mirrors but for software and polymost. But I suppose the bug could come from many other places.

My findings also.

View PostLeoD, on 16 July 2019 - 01:54 PM, said:

Compile-bisect says that r7736 is the culprit.

Awesome, thanks for doing that leg work! I don't compile EDuke32 so I rely on builds in Synthesis.
0

#7

Looking at the diff on 7736, there seems to be a whole lot of Polymost functions called if the renderer isn't the Software renderer, but that might not be appropriate to call if Polymer is used?

#ifdef USE_OPENGL
    if (videoGetRenderMode() != REND_CLASSIC)
        polymost_completeMirror();
#endif
 

0

#8

Still occurs in R7804. Seems like a critical bug to me so I'm surprised it's going on.

Are these forums the way to submit bugs? Is there a formal bug tracker like Bugzilla or Flyspray etc?
0

User is offline   oasiz 

  • Dr. Effector

#9

Forums are OK.
Polymer at the moment is lowest of the low priorities regarding dev due to all hands being on deck with dealing any remaining things for fury.
0

#10

View Postoasiz, on 18 July 2019 - 02:27 AM, said:

Forums are OK.
Polymer at the moment is lowest of the low priorities regarding dev due to all hands being on deck with dealing any remaining things for fury.


Wouldn't Iron Fury be using Polymer code though, or does it use Polymost?
0

User is offline   Lunick 

  • Snazzy Ex Tazzy

#11

View PostMitch Richters, on 18 July 2019 - 02:31 AM, said:

Wouldn't Iron Fury be using Polymer code though, or does it use Polymost?


Ion Fury uses Classic and Polymost only.
0

User is offline   oasiz 

  • Dr. Effector

#12

Polymer is an unfinished and unoptimized renderer with no dedicated dev or future path ahead at the moment, it's been mostly the same for the past ten years.
If it didn't offer a notable visual advantage to polymost, it would have been axed a long time ago.
0

#13

View PostLunick, on 18 July 2019 - 02:56 AM, said:

Ion Fury uses Classic and Polymost only.

Thanks for clarifying :)

View Postoasiz, on 18 July 2019 - 03:06 AM, said:

Polymer is an unfinished and unoptimized renderer with no dedicated dev or future path ahead at the moment, it's been mostly the same for the past ten years.If it didn't offer a notable visual advantage to polymost, it would have been axed a long time ago.

Thanks for the insight to this. It's amazing how out of date the Wiki is. It makes it sound like it's the future lol. I'll give up on it and stick to Software or Polymost :D.
0

User is offline   Mark 

  • Honored Donor

#14

Don't give up on Polymer so easily. Right from my start in modding back in 2009 Polymer has been my renderer of choice. Unfinished but very usable. But if you are mostly interested in the vanilla duke experience maybe the other renderers are a better choice for you. If your only issue with it so far is the black screen crash just go back and use an earlier version of eduke32. Its VERY COMMON for modders to use older versions during developement and release of their projects. Not encouraged but sometimes required.
0

#15

View PostMark, on 18 July 2019 - 03:50 AM, said:

Don't give up on Polymer so easily. Right from my start in modding back in 2009 Polymer has been my renderer of choice. Unfinished but very usable. But if you are mostly interested in the vanilla duke experience maybe the other renderers are a better choice for you. If your only issue with it so far is the black screen crash just go back and use an earlier version of eduke32. Its VERY COMMON for modders to use older versions during developement and release of their projects. Not encouraged but sometimes required.

I do like it better because its FOV feels more natural and less stretched in the corners (Polymost feels 2.75D, if that makes sense? Seems stretched further at the corners). Just feels very hit and miss though. Bug that's existed for months getting no love, lead developers working on Ion Fury have abandoned it, etc.

Don't worry though, as per the attached I have many scripts ready to chop and change between mods and renderers as necessary :)

Attached thumbnail(s)

  • Attached Image: scripts.PNG

0

#16

View PostMitch Richters, on 16 July 2019 - 02:40 PM, said:

Looking at the diff on 7736, there seems to be a whole lot of Polymost functions called if the renderer isn't the Software renderer, but that might not be appropriate to call if Polymer is used?

#ifdef USE_OPENGL
    if (videoGetRenderMode() != REND_CLASSIC)
        polymost_completeMirror();
#endif
 


These if statements were definitely the cause. Confirmed fixed in R7809 and tested with R7811.
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic


All copyrights and trademarks are property of their respective owners. Instead of reading this text, you could be playing Ion Fury! ;) © 2019 Voidpoint, LLC

Enter your sign in name and password


Sign in options