Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Faster than 40d, no problems

42 (26.1%)

Faster than 40d, problems

72 (44.7%)

No slower than 40d, no problems

14 (8.7%)

No slower than 40d, problems

16 (9.9%)

Slower than 40d, no problems

2 (1.2%)

Slower than 40d, problems

3 (1.9%)

Doesn't work (please explain)

12 (7.5%)

Total Members Voted: 160

[bhelyer]

Weirdly enough I disabled compiz and it's working fine.

Not weird at all. Compiz breaks ANYTHING OpenGL related on my system. And some stuff that isn't.

[Baughn]

There's no particular reason the output code should be running when you can't see the output anyway, or for that matter when the game's paused and you're not giving it input.

Unfortunately, most of that output code is in parts of DF I don't have access to, so there's nothing I can do about it.

[CobaltKobold]

well, yeah, the output code- I meant the game parts.

Though, minimizing/restoring with[PARTIAL_PRINT:YES:0]
[FRAME_BUFFER:NO]
[SINGLE_BUFFER:YES] makes it think it doesn't need to redraw anything, which is annoying- ha'e to enter some menu or other to get things 'isible again.

[Blank]

Yeah, pausing the game's FSM or whatever the programmer is using to update the game world and running a simple Windows message pump with appropriate sleep()s on lost focus is, I thought, standard operating procedure.

Haven't had a chance to try any of the new output builds, but I look forward to breaking your code on my Intel 945GM using hacked drivers. =D

(Did the new forum result in having to re-register?)

[Janus]

(Did the new forum result in having to re-register?)

Not normally, no:

Known issues:

(*) You must log-in using your Displayed name now.  The converter could only take one, so the separate user login name was dropped.  A few people were deleted because their displayed name had symbols that aren't used in this board.  Just let me know if that's you and I can put you back in the system.

[Phantasma]

With my laptop, 2 gb Ram and crappy intel onboard graphics card, d7 seems to be a huge improvement in FPS.

Btw, did I fuck up something with the tileset, or did the color brown got replaced by some yellowish color? My barrels and woodlogs are yellow...

[Jurph]

Try downloading Mike Mayday's tileset and looking at the included INIT.TXT file.  At the bottom there are color definitions that make the brown more pleasantly brown and bring out the brighter colors.  My only quarrel with Mayday's colors is if you happen to stumble on a yellow sand layer - it's blinding!

[Baughn]

There is one change in color handling on graphical tilesets, actually.

When DF applies its own colors on top of a tile, it does so by first grayscaling the tile. (This is actually done at startup.. regardless...) In 40d and before, this grayscaling was done by multiplying the color values (R, G and B) by 0.33 and then adding them. This, unfortunately, did not preserve luminance correctly..

As a fix, in 40d2 and above, the color components are weighted differently, preserving luminance but possibly producing odd effects in old tilesets. You may be seeing this.

[Quift]

I get some extremly annoying flickering window in Ubuntu. I didn't get it at first but after changing the tilesets to mike mayday (basicly by switching the art file and renaming the files .png aswell as changing their names in the mike mayday init folder.

Quite rough as a transfer surely.

I'm too new to linux to really know where I went wrong.

[Thndr]

for 40d7, I have to use PARTIAL PRINT or I get flickering.
And when a tooltip or something of that nature overlaps DF, DF re-overlaps the tooltip and displays all tiles as dots/same tile.

[Savok]

With my laptop, 2 gb Ram and crappy intel onboard graphics card, d7 seems to be a huge improvement in FPS.

Btw, did I fuck up something with the tileset, or did the color brown got replaced by some yellowish color? My barrels and woodlogs are yellow...

DF's brown IS dark yellow and looks like a sickly yellow color unless you've optimized colors on a good monitor.

[PolliMatrix]

In 40d7 full screen mode the frames per second are no longer limited by my display's refresh rate, but using any setting with [PARTIAL_PRINT:YES:2] always causes flickering. For most the flicker is parts of old frames and for SINGLE_BUFFER:YES it's part of the screen becoming blank for a short time.

In windowed mode PARTIAL_PRINT doesn't work without problems either: Sometimes, but not always it causes the type of flickering showing parts old frames. Using SINGLE_BUFFER makes the game display garbage as before.

In 40d6 there was no flickering when using PARTIAL_PRINT and if I set the FPS cap higher in 40d7 the flickering gets worse. A similar flickering problem was also present in the original 40d version.
Not using PARTIAL_PRINT works without problems in both windowed and full screen mode.

[Phantasma]

With my laptop, 2 gb Ram and crappy intel onboard graphics card, d7 seems to be a huge improvement in FPS.

Btw, did I fuck up something with the tileset, or did the color brown got replaced by some yellowish color? My barrels and woodlogs are yellow...

DF's brown IS dark yellow and looks like a sickly yellow color unless you've optimized colors on a good monitor.

I was already used to the mayday tileset, now I changed the settings in the init and the colors are correctly brown again.

[Baughn]

I get some extremly annoying flickering window in Ubuntu. I didn't get it at first but after changing the tilesets to mike mayday (basicly by switching the art file and renaming the files .png aswell as changing their names in the mike mayday init folder.

Quite rough as a transfer surely.

I'm too new to linux to really know where I went wrong.

"Renaming the files .png" <-- That's what.
You shouldn't call them .png unless they actually are PNG files; it'll fail to load them, producing all sorts of odd effects. (Unfortunately, while there's a 404-not-found check in there, it doesn't crash out if it just finds an empty tileset.)

BMP files should be called .bmp. They load fine.

[Sinergistic]

Bug/Error:

Not quite sure if I should make a new thread, or post this here, but here goes.

All of my autohotkey scripts are broken in 40d7. I did some testing, and it looks like sending {SHIFTDOWN/UP} and {ENTER} is broken. Sending normal key presses like the arrow keys seems to work ok, however.

I don't know if any of the previous 40d# versions have the same problem, but now that I've posted this, I give a few of them a try and see what happens.