[Micky C]

Thanks, problem solved.

New problem
r4908 mapster is giving a whole bunch of maps a level 5 corruption with a "sprite lists corrupted; error code 4; s=-1, i=16383", although previous versions of mapster32 are not giving this message.

Is this a false alarm, is it that these corruptions have always been there but undetected, or is it that the newer mapster is causing these corruptions? Scary stuff regarding the last two possibilities!

[TerminX]

What do you do to cause that?

[Jblade]

I remember you added a console variable to set the crosshair color, any way to access that ingame via con?

[Fox]

Parallaxed skies are screwed in resolutions lower than 640 x 480 (does anyone even use that?).

 Fox, on 06 December 2014 - 03:43 PM, said:

It's also because the weapon disappear if you switch while it is being raised:

While this has been fixed, now there is a problem with switching to another weapon while the current one is being lowered. This can be fixed by checking if weapon_pos ≥ 0 before switching. This will add a delay before switching weapon, but it will still alow to cycle through all weapons quickly as TX intended.

Edit: It seems wantweaponfire is not being used, is that intended?

[LeoD]

After correctly reproducing sergey808a's and darkprince227's environments I have to confirm a number of bugs:
- Polymer Cycloid Emperor's skin here and here.
- "boxy explosion" (animation frame messed up, here)
- missing arm when using the nuke button (here)
- missing vending machine texture (here)

Thanks, sergey808a and darkprince227, for reporting, and your patience.

plus:
0060_keycard.md3 fails to load on startup when using the Polymost Override Pack

All these bugs seem to be autoload related, and I have a feeling that they're initiated by the autoload scan issue I've reported yesterday.

[Fox]

BOUNCEMINE translucency is flickering Polymost. Dunno the heck is that.

Edit: Previous/next weapon keys are broken when using the Pipebomb trigger.

[LeoD]

 LeoD, on 13 January 2015 - 03:33 PM, said:

All these bugs [...], and I have a feeling that they're initiated by the autoload scan issue I've reported yesterday.

r4922 proves me wrong. Those issues have actually been introduced between r4633 (last OK version I could build), and r4639. And kplib.c is yet again among the suspects.

[TerminX]

What issues are left remaining?

[LeoD]

 TerminX, on 15 January 2015 - 12:59 PM, said:

What issues are left remaining?

Those linked in post #5105. It's extremely likely that they all have the same cause.

To reproduce you need the current HRP 5.3 ZIP, optionally the SC-55 Music Pack 4.0 (both also contained in the SFX package) from the HRP download page, and the matching Polymost HRP Override Pack 5.3.565 from here.

Put HRP + override into autoload and run EDuke32. The 0060_keycard.md3 load failure message will show up during startup already; the other bugs and more error log messages can be found when actually playing a level, e.g. E3L8.

Replace override by the music pack (others might do as well) to encounter the missing cycloid skin and the according error log message in E3L9.

Attached File(s)

•  eduke32-4633-OK-hrp+override.log (1.97K)
  Number of downloads: 251
•  eduke32-4639-ERR-hrp+override.log (2.05K)
  Number of downloads: 282
•  eduke32-4633-OK-hrp+music.log (2.59K)
  Number of downloads: 266
•  eduke32-4639-ERR-hrp+music.log (2.54K)
  Number of downloads: 281

[sergey808a]

 sergey808a, on 15 December 2014 - 12:03 AM, said:

When this bug will be fixed?
eduke32_win64_20141213-4814

At last, this bug has been fixed in eduke32_win64_20150115-4925.
I have been waiting this for a long time.
Thanks to the EDuke32 developers and thanks LeoD for detailed bugreport.

[LeoD]

 sergey808a, on 15 January 2015 - 11:28 PM, said:

I have been waiting this for a long time.

One month...

[darkprince227]

I've just tested the newest eduke build, and I'm glad to say that where I am, everything seems to be working like a charm!
No boxy exposions, Duke's auto-destruct punching hand is visible, the snack venders are Highres again, the Cycloid is full and the crosshair is yellow.

The only teeny-weeny problem I have is in the Duke Caribbean HRP which I've addressed in the VacaPlus HRP thread about the non-HRP weapons being invisible.

I'm glad I could help locate these bugs, and I'll be sure to keep you chaps updated on anything as I find them.

Thank you guys so much for everything, Hail to the HRP/eduke team, baby!

[sergey808a]

 LeoD, on 16 January 2015 - 07:23 AM, said:

One month...

Almost 5 month!!!

[Fox]

Is it possible to set THISACTOR for "globalsounds" in EVENT_SOUND?

[LeoD]

 sergey808a, on 16 January 2015 - 08:55 AM, said:

Almost 5 month!!!

Don't start counting before someone actually finds and reports a bug (this one on 2014-12-15, IIRC).

[Micky C]

Still experiencing some random crashing with the AMC TC with r4925, first reported here with an earlier build. However this time when I tried out the debug build, the game wouldn't even let me load a map!

Error message (no crashlog produced):


Log file: http://pastebin.com/raw.php?i=kzHjQcfP

Btw the level 5 corruption occurring when using the AMC TC's mapster script file is still happening unfortunately.

[Hendricks266]

Micky C, on 16 January 2015 - 03:20 PM, said:

Fixed.

I think you would have gotten a crashlog if you clicked Retry.

[Micky C]

Hendricks266, on 16 January 2015 - 04:37 PM, said:

I think you would have gotten a crashlog if you clicked Retry.

Me again. r4928. Pressing retry did not produce the crashlog.

[Jblade]

Is there a way to disable Megaton detection for a standalone mod? I swear I remember reading something added to the log in this effect. Every person who's having crash issues with the TC has Megaton installed.

[Micky C]

That bug's been fixed already. Keep up with the times
At least if you're referring to the startup problems. I really doubt that megaton would have anything to do with the in-game crashes or crash-on-exits.

[Jblade]

I don't get any of those at all though, apart from rare times when the screen is rotating. It's hard for me to help track down and find out where the problem is (and if it's my fault) because most of the time people are just saying "I get crashes" without any more specifics.

I tracked down the L5 corruption error to the event analyzesprites in my M32 script file, here's what it looks like:

Spoiler

onevent EVENT_ANALYZESPRITES

    var ts ow pic z
    var k onumtspr

    ife showrespawn_always 0
    {
        ifaimingsprite ife sprite[searchwall].picnum RESPAWN nullop
        else break
    }

    set onumtspr spritesortcnt

    for ts range onumtspr
    {
        set ow tsprite[ts].owner
        ife showrespawn_always 0 ifn ow searchwall nullop else
        {
            ife sprite[ow].picnum RESPAWN
            {
                set k spritesortcnt
                tdupsprite ow

                // XXX: doesn't work with E1L5 boss RESPAWN...
                // Something's wrong with setting tsprite[] members.
                sub tsprite[k].z 4096

                set tsprite[k].xrepeat 32
                set tsprite[k].yrepeat 32

                set pic sprite[ow].hitag
                ifge pic 0 ifl pic MAXTILES
                    set tsprite[k].picnum pic

                and tsprite[k].cstat 0xfffffdff  // clear bit 512 (reverse translucency)
                or tsprite[k].cstat 2  // set bit 2 (33% translucency)
                ifvarn showrespawn_fulltrans 0
                    or tsprite[k].cstat 512
            }
			
            ife sprite[ow].picnum 14
            {
                set k spritesortcnt
                tdupsprite ow

                // XXX: doesn't work with E1L5 boss RESPAWN...
                // Something's wrong with setting tsprite[] members.
                sub tsprite[k].z 4096

                set tsprite[k].xrepeat 32
                set tsprite[k].yrepeat 32

                set pic sprite[ow].hitag
                ifge pic 0 ifl pic MAXTILES
                    set tsprite[k].picnum pic

                and tsprite[k].cstat 0xfffffdff  // clear bit 512 (reverse translucency)
                or tsprite[k].cstat 2  // set bit 2 (33% translucency)
                ifvarn showrespawn_fulltrans 0
                    or tsprite[k].cstat 512
            }
			
			
            ife sprite[ow].picnum 16011
            {
                set k spritesortcnt
                tdupsprite ow

                // XXX: doesn't work with E1L5 boss RESPAWN...
                // Something's wrong with setting tsprite[] members.
                sub tsprite[k].z 4096

                set tsprite[k].xrepeat 32
                set tsprite[k].yrepeat 32

                set pic sprite[ow].hitag
                ifge pic 0 ifl pic MAXTILES
                    set tsprite[k].picnum pic

                and tsprite[k].cstat 0xfffffdff  // clear bit 512 (reverse translucency)
                or tsprite[k].cstat 2  // set bit 2 (33% translucency)
                ifvarn showrespawn_fulltrans 0
                    or tsprite[k].cstat 512
            }
			
			
            ife sprite[ow].picnum 1232
				{
				set pic sprite[ow].lotag
				ifvarg pic 0
					{
									set k spritesortcnt
					tdupsprite ow

					// XXX: doesn't work with E1L5 boss RESPAWN...
					// Something's wrong with setting tsprite[] members.
					sub tsprite[k].z 6096

					set tsprite[k].xrepeat 32
					set tsprite[k].yrepeat 32

		
					
					ifl pic MAXTILES
						set tsprite[k].picnum pic

					and tsprite[k].cstat 0xfffffdff  // clear bit 512 (reverse translucency)
					or tsprite[k].cstat 2  // set bit 2 (33% translucency)
					}
				}

            ife sprite[ow].picnum FIRSTGUNSPRITE
				{
				                set k spritesortcnt
                tdupsprite ow

                // XXX: doesn't work with E1L5 boss RESPAWN...
                // Something's wrong with setting tsprite[] members.
                sub tsprite[k].z 4096

                set tsprite[k].xrepeat 32
                set tsprite[k].yrepeat 32

				ife sprite[ow].xvel 0 setvar pic 3587
				ife sprite[ow].xvel 1 setvar pic 5245
				ife sprite[ow].xvel 2 setvar pic 5501
				ife sprite[ow].xvel 4 setvar pic 6400
				ife sprite[ow].xvel 8 setvar pic 6013
				ife sprite[ow].xvel 16 setvar pic 6336
				ife sprite[ow].xvel 32 setvar pic 6656
				ife sprite[ow].xvel 64 setvar pic 6429
				ife sprite[ow].xvel 128 setvar pic 6912
				ife sprite[ow].xvel 256 setvar pic 16384
                ifge pic 0 ifl pic MAXTILES
                    set tsprite[k].picnum pic

                and tsprite[k].cstat 0xfffffdff  // clear bit 512 (reverse translucency)
                or tsprite[k].cstat 2  // set bit 2 (33% translucency)
				}
				
            ife sprite[ow].picnum SHOTGUNSPRITE
				{
				                set k spritesortcnt
                tdupsprite ow

                // XXX: doesn't work with E1L5 boss RESPAWN...
                // Something's wrong with setting tsprite[] members.
                sub tsprite[k].z 4096

                set tsprite[k].xrepeat 32
                set tsprite[k].yrepeat 32

				ife sprite[ow].xvel 0 setvar pic 3587
				ife sprite[ow].xvel 1 setvar pic 5245
				ife sprite[ow].xvel 2 setvar pic 5501
				ife sprite[ow].xvel 4 setvar pic 6400
				ife sprite[ow].xvel 8 setvar pic 6013
				ife sprite[ow].xvel 16 setvar pic 6336
				ife sprite[ow].xvel 32 setvar pic 6656
				ife sprite[ow].xvel 64 setvar pic 6429
				ife sprite[ow].xvel 128 setvar pic 6912
				ife sprite[ow].xvel 256 setvar pic 16384
                ifge pic 0 ifl pic MAXTILES
                    set tsprite[k].picnum pic

                and tsprite[k].cstat 0xfffffdff  // clear bit 512 (reverse translucency)
                or tsprite[k].cstat 2  // set bit 2 (33% translucency)
				}
				
				
        }
    }

    for i drawnsprites
    {
        set j tsprite[i].owner
        switch sprite[j].picnum
        case 1404 // FAKE PLAYER
		ife sprite[j].extra 0 set tsprite[j].picnum 5245 // James 
		ife sprite[j].extra 1 set tsprite[j].picnum 5501 // Zaxtor 
		ife sprite[j].extra 2 { set tsprite[j].picnum 6400 ifspritepal 0 set tsprite[j].pal 21 } // Merlijn
		ife sprite[j].extra 3 { set tsprite[j].picnum 6013 ifspritepal 0 set tsprite[j].pal 11 } // Highwire
		ife sprite[j].extra 4 { set tsprite[j].picnum 6336 ifspritepal 0 set tsprite[j].pal 21 } // Sang
		ife sprite[j].extra 5 { set tsprite[j].picnum 6656 ifspritepal 0 set tsprite[j].pal 12 } // Rusty
		ife sprite[j].extra 6 { set tsprite[j].picnum 6429 ifspritepal 0 set tsprite[j].pal 21 } // Geoffrey
		ife sprite[j].extra 7 { set tsprite[j].picnum 6912 ifspritepal 0 set tsprite[j].pal 11 } // Mikko
		ife sprite[j].extra 13 set tsprite[j].picnum 16384  // Micky
		break
		case 1405
		set tsprite[j].picnum 1404
		break
		case 490
		case 10037
		case 5868
		case 5869
		case 1095
		case 3375
		case 14296
		case 3792
		case 1020
		case 7676
		case 2271
		case 2311
		case 7038
		case 17133
		case 11772
		case 8623
		case 9175
		case 9433
		case 18225
		case 18224
		case 16290
		case 16327
		case 10613
		case 13949
		case 13950
		case 13951
		case 13952
		case 11309
		case 11686
		case 16234
		case 16292
		case 17128
		case 17129
		case 17130
		case 17131
		case 17323
		case 18333
		case 18428
		case 18429
		case 18431
		case 18473
		case 18646
		case 18647
		case 18648
		case 18649
		case 19619
		case 19620
		case 19621
		case 19622
		case 19712
		case 19713
		case 19714
		case 19715
		case 19716
		case 19717
		case 19718
		case 19719
		case 19720
		case 19721
		case 19722
		case 19723
		case 19724
		case 19725
		case 19726
		case 19727
		case 19728
		case 19729
		case 19730
		case 19731
		case 19732
		case 19733
		case 19734
		case 19735
		case 19736
		case 19737
		case 19738
		case 19739
		case 19740
		case 19741
		case 19742
		case 19743
		case 19744
		case 19745
		case 19746
		case 19747
		case 19748
		case 19749
		case 19750
		case 19751
		case 19752
		case 19753
		case 19754
		case 19755
		case 19756
		case 19757
		case 19623
		case 19624
		case 19625
		case 19626
		case 19627
		case 19628
		case 19629
		case 19630
		case 19631
		case 19632
		case 19654
		set sprite[j].blend 255
		break
        endswitch
    }
endevent

I'm still shit at M32 script so you might be able to spot right away what the problem is.

[Fox]

The Shrinker is not being selected with Next Weapon if subweapon is set.

Edit: You can switch weapons during reloading in the DOS version. Oddly enough, that seems to be intended looking at the source code.

[Helixhorned]

Micky C, on 16 January 2015 - 08:22 PM, said:

Me again. r4928. Pressing retry did not produce the crashlog.

C-CON lacks some necessary checks for whether the tile passed to the *shoot* commands is in fact valid.

[Fox]

Is it possible to add an .htflag to spawn JIBS6 like hard-coded enemies?

[Jason S.]

Forgot I even had an account on here!

Anyways, i'd just like to bring up the obvious efficiency issue plaguing Polymer due to a lack of graphical options and sliders. Skyrim, other Bethesda games (even a few with ENB), Serious Sam HD and other more complex games run so well on my older ATI Radeon HD 6670 (25-60fps on average) at full resolution (1600x900) under some really great settings, yet this low poly sector based game doesn't with Polymer at any resolution or setting, becoming unplayable very quickly even at 640x480 under the lowest texture setting. To note, Polymost runs at hundreds of frames per second with the highest available settings (that is just the two, screen and texture resolution ).

Its the number of lights that does it (Duke Burger is a nightmare), so i'm wondering if there's a way to make Polymer more efficient with more "advanced" menu options and sliders in the future, such as limiting the draw distance of real time lights, specular and shadow effects, turning off parallax and specular mapping separately, and changing the shadow resolution itself. The "advanced" menu has a massive empty space where these options could be placed, and i'm pretty sure this doesn't require a huge restructuring of the engine to implement.

The problem is that, the core effect of Polymer should run more or less as it appears it should, and perform the same or better than the above games. Polymer should not be left to the those with the best of cards when the core effect doesn't need them. I think this should be a must if more effects are going to be implemented in the future, as everyone's going to run into this problem sooner or later, and i'm sure only a few adjustments will have Polymer running way better on everyone's hardware, without too much quality degradation.

Thanks.

[The Commander]

Most of the variables you asked about can be changed in the console at the moment using r_pr_ followed by the name of the variable.

[Micky C]

Jason S., on 24 January 2015 - 11:18 PM, said:

The problem is that, the core effect of Polymer should run more or less as it appears it should, and perform the same or better than the above games. Polymer should not be left to the those with the best of cards when the core effect doesn't need them. I think this should be a must if more effects are going to be implemented in the future, as everyone's going to run into this problem sooner or later, and i'm sure only a few adjustments will have Polymer running way better on everyone's hardware, without too much quality degradation.

It's no secret that polymer has long been unoptimised. The good news is that it should run much, much faster when it's closer to finished. I've heard that someone may be working on improving it at the moment, however what the end result of this is or when it'll be made public could be anyone's guess.

[Hendricks266]

Fox, on 13 January 2015 - 03:41 PM, said:

Edit: Previous/next weapon keys are broken when using the Pipebomb trigger.

Fox, on 17 January 2015 - 01:46 PM, said:

The Shrinker is not being selected with Next Weapon if subweapon is set.

Fixed.

[Fox]

Fox, on 13 January 2015 - 03:41 PM, said:

Edit: Previous/next weapon keys are broken when using the Pipebomb trigger.

I was referring to a different problem, which appears to have been fixed since then. The rest was just like the DOS version, but the change is welcome.

Now a minor remaining problem with previous/next weapon keys. When you have no pipebomb ammo left, but there is still a pipebomb in the ground, you still can switch to the pipebomb trigger by pressing 6, but not with next/previous weapon.

[Jason S.]

The Commander, on 24 January 2015 - 11:44 PM, said:

Most of the variables you asked about can be changed in the console at the moment using r_pr_ followed by the name of the variable.

Thanks for the info. Found the list of Polymer commands too and tested it a bit. Of course, the console only allows you to change the number of overall lights and passes in total, yet the framerate still doesn't compare to Polymost's or my other games, and can still hit 12-20fps and just stay there for a long while. Most games use a draw distance for the effects, and i'm pretty sure that many super smooth games like Uncharted 2/3 would run like crap too if they extended the shadow and lighting draw distance almost to infinity like Polymer does at the moment.

It did help to an extent, but it wasn't the performance boost I expected. Removing certain effects didn't do as much as I expected, either. In the end, i'm betting on there also being an overall engine and/or shader usage efficiency problem which will have to be isolated later on. In detail, beforehand, the game would get up to 30-60fps with VSYNC on at maximum, even during Critical Mass's explosive ending or under a large shadow spotlight or two, its just that it's way too easy for it to begin lagging badly too, in either big areas or just in general too.

Perhaps in the future, I'll get something like 20-30fps on average.

Micky C, on 25 January 2015 - 02:21 AM, said:

It's no secret that polymer has long been unoptimised. The good news is that it should run much, much faster when it's closer to finished. I've heard that someone may be working on improving it at the moment, however what the end result of this is or when it'll be made public could be anyone's guess.

I kinda forgot this thing was unfinished as its been out for several years now.

As for what this other person might be doing, i'm hoping it is some sort of tweak or the addition of advanced graphics options at least (so people don't have to use the console). Maybe it's just a set of maphack files which decreases the number of lights save for the shadow map spots. Seems like good news if it happens.