Print

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

[Footkerchief]

You should mention the bug in the DF bug forum; it's not a libgraphics problem. However, doing so is probably pointless right now.

It's your input code, since this cannot happen in d16, as I pointed out in that thread.

It's probably what Toady mentioned in the first reply: "I had to restructure every screen in the game with the potential to break anything related to any screen."  Nobody who's working on the code is paying much attention to Bug Reports at the moment, so I don't know where those reports should go, if not here.

[Baughn]

They should go under "known bugs". Fixing it now is pretty pointless, as Toady would have to do that work over again later anyway, and it isn't a really important one if you're aware of it.

So done..

[Zared]

Tried the Linux version.  Frame rate is about 1/2 what the same save file is under Windows, regardless of what render mode I use.  Also, it only runs once.  If I quit and run the game again, the sound in the intro is mostly scratchy static, though the music in-game sometimes works, and I get about 6 fps and the interface lags behind key presses by 1 or 2 seconds.  Only way to fix it is to restart X. 

It turns out the massive slowdown if I run df a second time without restarting X is due to Compiz Fusion running, even if no fancy effects are happening.  It's completely unrelated to the sound system also breaking.  It actually slows it down the first time, too, just not by as much. 

If I turn Compiz off, I get a nice 19 fps for all modes except standard, which gets 16, and 2D, which get 9, and no interface lag.  This is pretty comparable to Windows on the same machine, though a few FPS slower.

[Baughn]

Can you try 2DHW and 2DASYNC, tell me how those work?

It's possible that 2D should just be 2DHW, I think I was being way too conservative there.

[isitanos]

"Any linux user can install the LSB" simply isn't accurate, unfortunately. In particular, it doesn't exist on Arch, meaning at least that I wouldn't be able to run DF.

Oops, didn't know that. Yeah, the situation is really complicated...

[lizard]

I'm willing to volunteer a little time, but am not sure what you want / need at this point.

I have 2 boxes, both old.  A single-core p4 + old (FX5200?) AGP card running ubuntu 9.10 and a little more modern box running debian lenny.  Should I download the binaries, download source and compile, what settings should I play with, etc?

[iambap]

Is it recommended to use my old d16 save or start a completely new fort with this version?  or both?  or neither?

I'm on windows xp and probably won't be using 2d modes (maybe experimentally if I think about it) if that makes a difference.

[Baughn]

Well, the 3D modes are pretty much broken on d17. There's a very good chance it'll crash. It's fixed now, but..

The saves should be compatible, though.

[iambap]

Well, the 3D modes are pretty much broken on d17. There's a very good chance it'll crash. It's fixed now, but..

The saves should be compatible, though.

Thanks.

I guess what I really want to know is which (using old saves or a brand new save) would be better for submitting bug reports.  I was thinking I could help by submitting bug reports for the newly redone UI.  Maybe that's not what your looking for, though.

[Baughn]

Not really, no. The UI code that Toady has adapted is pretty much irrelevant; there's no point in fixing glitches in there, since he'd have to redo the job when he eventually ports the IO code forward to the 2010 release.

On the other hand, bug reports relating to keyboard input and video output are quite welcome. Those are things that won't change, or need to be rewritten.

[SirPenguin]

Alright, doing some testing. First on my laptop. Desktop later on.

Intel Core Duo, 1.8ghz processor
2gigs of RAM
965g Intel integrated graphics chip
used window mode and maximized the window
Tested on a "mature", 100+ dwarf fortress with some liquid stuff going on

Standard: 17
2D: 16
2DHW: 16
2DASYNC: 15
PARTIAL:0: 19
ACCUM_BUFFER: 7
FRAME_BUFFER: Crashed every time I tried to maximize the window
VBO: 18

[tychoruniko]

Just a quick bug; when you are using the site finder and press the "cancel" button while it is still searching, the search continues while you can move the embark rectangle, but then the search finishes but doesn't move the rectangle to the found site.

[Heliman]

So, this is the new version, raw and unrefined but with the promised features? or am I wrong?

[Lord Shonus]

I'll answer so the people sick of answering don't have to. No. This is simply the last version of the improved rendering code for 40d.

[Pita]

Some adventure mode quirks that I think are new to d17 for me:

The last announcement flickers inbetween steps every now and then. When this starts to happen it seems to create a lot of lag too.

When moving on the map, the player seems to flick back and forth between the current location and destination--usually only on the first step.

Also, combat announcements seem to require a key-press or two to continue play, even when they are only one line. The screen doesn't refresh immediately either. For example, when moving from the wrestle screen after selecting your option, the combat announcement will display, but the wrestling interface will still be present. Then on a second key press, the screen will either remain the same or change back to the normal adventuring display, only frozen (no moving water etc.). Lastly, another key press returns to normal gameplay. A normal attack seems to freeze and return with one key press.

The other main annoyance is one that isn't new for d17 though, where I can't escape after dying.

I'm not sure if these are UI bugs, or keypress/video output bugs. I'm using windows XP, ol' laptop with intel integrated graphics card