Duke4.net Forums: something's gone wacky with polymost - Duke4.net Forums

Jump to content

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

something's gone wacky with polymost

User is offline   Ninety-Six 

#1

So after updating my eduke the previous time, polymost has become absolutely unplayable. It doesn't matter if I load a mod or go vanilla, something's gone weird.


I know the renderer was updated recently and that may have something to do with it, plus I am stuck with an older machine because i am a poor boy. If that's the sole reason then I understand, though that kinda sucks...


That being said, I can't help but wonder if there's something more going on.


Case in point, when the game starts, the colors are warped:
Spoiler


The colors are corrected in-game, but at that point I'm playing at a whopping 15 fps:
Posted Image


And no amount of messing with the display options will fix it.


Something else I want to mention. the classic renderer is still fine, but when it boots there's a blank white screen for about 5 seconds before it actually starts the title sequence. This doesn't happen when ran in Polymost. For some reason. I don't know if that means anything but I thought I'd mention it.


I don't think there'll be anything helpful in it but I've attached the eduke log.


These were all taken with the newest snapshot r7138, but at least the frame rate problem started with r6775 (of the versions I have, anyway). I don't know if the polymost renderer was updated by then or not. The latest version I have where it worked fine is r6576.

Attached File(s)



This post has been edited by Ninety-Six: 03 November 2018 - 02:02 AM

0

User is offline   Ninety-Six 

#2

Small update: I noticed something that may or may not be interesting.


"Correlation does not imply causation" and all that, to be quite frank I don't even know what this line means or what it's supposed to look like (for all I know this is perfectly normal), but across the three versions I mentioned:


r6576 (the one that works) has the line "Initialized 24.0M cache"

r6775 (the earliest one I have where the framerate issues began) has the line "Initialized 64.0M cache". I point this one out because in this snapshot, I get an average of 22 fps. Still not good, but does give me 7 extra frames for an unknown reason.

and then of course, r7138, has the line "Initialized 96.0M cache."


Again, maybe this is perfectly normal and this is simply just how it's supposed to work. I don't know, but at this point I'm providing whatever information I can in hopes of explaining the wackiness. I just noticed this little correlation between rising cache size and frame rate.

This post has been edited by Ninety-Six: 03 November 2018 - 03:51 AM

0

User is offline   Micky C 

  • Honored Donor

#3

"Correlation does not imply causation" refers to two sets of data that appear to follow the same trend (i.e as one increases, the other also increases), however there is no possible connection between the two. For example, the polymost framerate on your computer on a given day would not be related to the number of solar flares in the Andromeda galaxy on that day, even if they are both high at the same times.

Since you've observed changes in the log which corresponds to changes in the framerate, it's entirely possible they may be related. It's also possible they may not be related, but the phrase should not be used in this case, just like it shouldn't be used by the U.S government saying that Iran not working on nuclear weapons was completely unrelated from the fact that Iran had a deal where they weren't allowed to work on nuclear weapons Posted Image
0

User is offline   Maisth 

#4

Mapster32 suffers somewhat of the same problem with Polymost, atleast for me, when searching for a texture, all the textures appear either pitch black or are just translucent black, and its hard to see it, only happens on Polymost, with Classic its stable.

This post has been edited by Maisth: 03 November 2018 - 05:13 AM

0

User is offline   Ninety-Six 

#5

 Micky C, on 03 November 2018 - 03:59 AM, said:

-snip-


When I said "I don't know what this line means" I actually was referring to the line in the code, just to be clear.


I said that just to acknowledge that the thing I noticed between frame rates and cache size may literally be nothing at all, but at the same time, might have been something.
0

User is offline   Mark 

#6

Whenever I install a different revision I always delete my textures and texture cache files and let them rebuild the next time Eduke32 runs. That has solved a lot of graphics glitches over the years. Your framerate issue, no idea.
0

User is offline   Ninety-Six 

#7

 Mark, on 03 November 2018 - 10:44 AM, said:

Whenever I install a different revision I always delete my textures and texture cache files and let them rebuild the next time Eduke32 runs. That has solved a lot of graphics glitches over the years. Your framerate issue, no idea.


I gave this a shot.

Didn't really have an effect. If there was, I think it just made the white screen appear in Polymost too, though only for half a second. But to be honest I'm not sure if that was already there and just wasn't looking for it. Colors were still warped on the logos.

Log file still says 96.0M cache, if that's important to anyone.
0

User is offline   oasiz 

  • Dr. Effector

#8

Updated your GPU drivers ?
I recall testing somewhat recent versions with HD2000 and I've had no issues.
0

User is offline   Ninety-Six 

#9

 oasiz, on 04 November 2018 - 02:49 AM, said:

Updated your GPU drivers ?
I recall testing somewhat recent versions with HD2000 and I've had no issues.

Says they're up to date.
0

User is offline   Forge 

  • Speaker of the Outhouse

#10

 Ninety-Six, on 04 November 2018 - 02:21 AM, said:

Log file still says 96.0M cache, if that's important to anyone.

It isn't


Kind of a silly question, but you did try the snapshot by making a clean folder and putting nothing but the duke3d.grp file and the snapshot in it & run it from there?
0

User is offline   Ninety-Six 

#11

 Forge, on 04 November 2018 - 05:59 AM, said:

It isn't


Kind of a silly question, but you did try the snapshot by making a clean folder and putting nothing but the duke3d.grp file and the snapshot in it & run it from there?


No but I did do that for r6775, the one where the issues began.


Not that I keep anything in the main root that would interfere with runtime. It's only batch files, text files, and con files that I make sure are not named the same as the ones in the original game.
0

User is offline   pogokeen 

  • EDuke32 Developer

#12

Hi Ninety-Six,

Thanks for the report and sorry that you're running into this issue.

Could you enter the command "glinfo" in the console and upload the resulting log file here?

I will investigate this issue in December as soon as I can. I'll keep this thread updated on my progress.
1

User is offline   Ninety-Six 

#13

 pogokeen, on 07 November 2018 - 06:35 PM, said:

Hi Ninety-Six,

Thanks for the report and sorry that you're running into this issue.

Could you enter the command "glinfo" in the console and upload the resulting log file here?

I will investigate this issue in December as soon as I can. I'll keep this thread updated on my progress.


Can do.


Like I said. I wouldn't be surprised if it was age but the warped colors make me wonder if it might be something else:

Attached File(s)


0

User is offline   Ninety-Six 

#14

 pogokeen, on 07 November 2018 - 06:35 PM, said:

I will investigate this issue in December as soon as I can. I'll keep this thread updated on my progress.


I ask out of curiosity, not impatience: Has any progress been made on this front as of now?
0

User is offline   Ninety-Six 

#15

As of r7352, this is still an issue, and almost everything remains the same. A notable change is that the FPS for the first section of Hollywood Holocaust has doubled to almost 30 fps, and the framerate limiter does not seem to affect it. Nevertheless it is not consistent and still in the red.
0

Share this topic:


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


All copyrights and trademarks not owned by Voidpoint, LLC are the sole property of their respective owners. Play Ion Fury! ;) © Voidpoint, LLC

Enter your sign in name and password


Sign in options