[TerminX]

Just get something with recent NVIDIA hardware that's at least a bit better than the lowest of the low end and you'll be set. You'll want at least 2 gigs of RAM so you can comfortably run a modern OS (Windows 7) and be able to run games without hitting the pagefile much, and any reasonably speedy dual core CPU (or quad, if there's a quad core laptop and you're made of money) should be fine.

The main thing to keep in mind if Polymer performance is a primary concern is to remember that no matter what your personal preferences have been in the past in terms of video card vendor, Polymer will always run better on NVIDIA hardware because, well, Plagman works there.

[Stabs]

you will probably want an 8800 minimum

which is also basically a 9800 / gts240

for best performance you will probably want a gtx260 / gtx280 if you can afford it.

[TerminX]

Better widescreen support:

[TerminX]

Btw, mods that use rotatesprite will want to make note of two new bits in "orientation"... value 256 will align something to the left of the screen and 512 will align something to the right.

Without the new bits set, stuff will render in the center of the screen, like this:

[Hendricks266]

TX, on Jun 17 2010, 09:06 PM, said:

Better widescreen support:

Incredibly awesome.

[TerminX]

This needed fixing too:

[Fox]

Hmm, there is something I should ask about widescreen support...

I don't know if you already fixed it, but the widescreen is made like as if the default resolution aspect ratio is 320x240, while it should be 320x200...

[SwissCm]

Fox, on Jun 19 2010, 11:28 PM, said:

Hmm, there is something I should ask about widescreen support...

I don't know if you already fixed it, but the widescreen is made like as if the default resolution aspect ratio is 320x240, while it should be 320x200...

320x200 is supposed to be run at 4:3 (with rectangular pixels) not 16:10.

[MusicallyInspired]

Ah the days when pixels weren't square.....sigh...

[Tetsuo]

Aren't you getting that backwards? 320x200 was run with rectangular pixels. Not the other way around... we didn't move to rectangular pixels.

[Jokke_r]

seeing as everything was run on 4:3 monitors which aspect ratio is 1.333...

320:200 = 1.6 = 16:10 = non-square pixels when stretched out on a 4:3 monitor.

320:240 = 1.333... = 4:3 = square pixels on a 4:3 monitor.

[SwissCm]

Tetsuo, on Jun 20 2010, 05:52 PM, said:

Aren't you getting that backwards? 320x200 was run with rectangular pixels. Not the other way around... we didn't move to rectangular pixels.

That's... what I said.

[Tetsuo]

I was responding to MusicallInspired.

[SwissCm]

Working on making widescreen versions of the original hud weapon artwork.

Tetsuo, on Jun 20 2010, 08:54 PM, said:

I was responding to MusicallInspired.

oh, derp

[Fox]

Cool! You are good on sprite editing


That will most likely be used in DukePlus


To help you:

[MusicallyInspired]

Tetsuo, on Jun 20 2010, 05:54 AM, said:

I was responding to MusicallInspired.

What? I didn't say that.....

[TerminX]

I haven't seen any weirdness in a while, so I've upgraded the compiler chain used to generate the synthesis builds to gcc 4.5.0. r1659 is the last gcc 4.3 build.

[Danukem]

TX, on Jun 23 2010, 01:32 AM, said:

I haven't seen any weirdness in a while, so I've upgraded the compiler chain used to generate the synthesis builds to gcc 4.5.0. r1659 is the last gcc 4.3 build.

Since TX isn't one to toot his own horn, let me point out that r1658 (and later) include some extremely important fixes to the sound system of problems that had led to hitching, lockups, and various sound failures which have been plaguing EDuke32 ever since the new sound system was adopted from JF last year. One lockup had been fixed by Plagman a while back, but other bugs were hiding under the carpet and would come out and bite after about 30 minutes of gameplay (sometimes much sooner). It took hours of hard work to hunt down those bugs, and the result is what seems to be the most stable and bug free EDuke32 that we've had in a long time *mentally crosses fingers*.

[TerminX]

That's true, I did have to stay up until 6 in the morning a couple of times hunting down some of those frustrating sound problems. Things should be pretty solid now, though I would like to be able to at some point debug that remaining hang you got a couple of times in WGR2. Hang or not, things are in a way better state than they were a week or month ago, so everyone would be wise to pick up a new build soon. The sound system had so many problems that I've honestly lost track of how many fixes were needed to get it to where it is now.

Fuck corner cases.

[Hendricks266]

I will continue using gcc 4.3.3 until further notice.

[Tea Monster]

Just to say thank you for all the hard work. I still love playing Duke and it's wonderful to see all the work going into making it better.

[Another Duke Fan]

I have serious mouse conrol issues. X-axis is disabled and movement is sluggish and irresponsive. My mouse is Razer Boomslang.

[Mblackwell]

Is this a recent thing? Have you tested EDuke32 with the same mouse before? Are there any other control devices plugged in?

Follow the White Rabbit

[The Commander]

@Another Duke Fan
Delete your .cfg files, if the problem still continues make a new thread with the stuff the white rabbit states.

[Jblade]

TerminX, do you know if you can add an event of some kind that'll let us display sprites and stuff on the help screen? or is there already something like that available? I'm going to add in some form of help system to my mods but being able to display stuff dynamically on the help screen would help a huge amount

[TerminX]

Heh, yeah, actually, I just happened to leave the F1 help in current (last few revisions) builds of EDuke32 in an unfinished state that lets you do what you want to do. When I made the changes recently to have rotatesprite be widescreen aware it was easier for me to just disable the help screen based around the "show_help" member of the userdef struct and have F1 open the regular help item from the menu (with some changes made to bring you back to the game when pressing esc instead of bringing you to the main menu).

You should be able to just look up the menu id number out of menus.c and draw onto it using EVENT_DISPLAYMENU or something of that nature. Just be prepared to rewrite it in 6 months or a year or whenever I get around to writing a new menu system.

[Jblade]

cool, I'll see what I can do - thanks!

[Hendricks266]

TX, on Jun 29 2010, 09:58 AM, said:

writing a new menu system

[TerminX]

Nooooooo, don't take my quotes out of context. It's something that needs to be done but it probably won't be soon!

[Hendricks266]

That's what you said about... everything since OGG support. I'm patient.