Print

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

Yes

0 (0%)

No

0 (0%)

Total Members Voted: 0

[x2yzh9]

I'm getting an error. I DL the file, but the only thing in it is the data folder, command line.txt, and compress_bitmaps.bat. What's wrong? Can someone upload their personal file of DFG30 so I can play?

[Djohaal]

1680

Darn, that means I'll need a new monitor to enjoy the 21 pix bliss of DFG....

[Fluff]

Hi. I'm currently using a 1024X768 moniter( ), and I know the site says there's no workaround for the 1280 pixel requirement, but what I can I do to make it look best. I know there'll be no way to make it perfect, but which Init settings will it work best with?

[hermano]

Hi. I'm currently using a 1024X768 moniter( ), and I know the site says there's no workaround for the 1280 pixel requirement, but what I can I do to make it look best. I know there'll be no way to make it perfect, but which Init settings will it work best with?

You might try these settings, but it will, of course, look bad (assuming fullscreen):
[GRAPHICS_FULLSCREENX:1024]
[GRAPHICS_FULLSCREENY:768]

[GRAPHICS_BLACK_SPACE:YES]
and
[FULLGRID:80:60]

[Fluff]

Hi. I'm currently using a 1024X768 moniter( ), and I know the site says there's no workaround for the 1280 pixel requirement, but what I can I do to make it look best. I know there'll be no way to make it perfect, but which Init settings will it work best with?

You might try these settings, but it will, of course, look bad (assuming fullscreen):
[GRAPHICS_FULLSCREENX:1024]
[GRAPHICS_FULLSCREENY:768]

[GRAPHICS_BLACK_SPACE:YES]
and
[FULLGRID:80:60]

Thanks. It's not perfect, but given how computers generally blend with me, I'm thankful that it works at all.

[Baron von Eptastic]

Hey guys,

First off, I'd like to thank Mayday for some great work!  I've been playing DF for a couple months now, and I just can't play it without your tileset.

Secondly, I have an awful newbie question that I can't quite seem to figure out.  After I installed the latest version of your tileset, the top inch or so of my screen isn't visible.  Its to the point that when I'm on the embark screen, I can't see the first dwarf in the list.  I've tried googling the problem and I've checked your FAQ, but I haven't been able to figure out how to fix it. 

Here's a screenshot:

Spoiler (click to show/hide)

And here's the resolution section from my init.  I play in windowed:

Spoiler (click to show/hide)

[WINDOWEDX:1280]
[WINDOWEDY:800]
[FONT:maydayMIN.bmp]


[FULLSCREENX:1680]
[FULLSCREENY:1050]
[FULLFONT:maydayMIN.bmp]


[BLACK_SPACE:YES]


[GRAPHICS:YES]
[GRAPHICS_WINDOWEDX:1280]
[GRAPHICS_WINDOWEDY:800]
[GRAPHICS_FONT:mayday.bmp]
[GRAPHICS_FULLSCREENX:1680]
[GRAPHICS_FULLSCREENY:1050]
[GRAPHICS_FULLFONT:mayday.bmp]
[GRAPHICS_BLACK_SPACE:YES]


[GRID:80:50]
[FULLGRID:105:65]

Any ideas would be greatly, greatly appreciated.

[forsaken1111]

Could it have something to do with your odd screen arrangement, with the taskbar on the right?

Have you tried it with the taskbar on the bottom?

[Mike Mayday]

What is your screen resolution?

[Baron von Eptastic]

I normally have the taskbar on the bottom of the screen, but I have to move it to the right side when I play df or else I'd miss out on some of the bottom of the window, as well.  Having the taskbar on the bottom doesn't change the problem with the window at all.

I'm using an HDTV as a monitor, and as such the native resolution is a little screwy.  I'm running it at 1360x768. 

However, I've never had this issue before.  There were no problems with 40d when I used your tileset.  And I just confirmed that I don't have this issue when I run df2010 with the default tileset. 

Thanks for the quick responses, guys!

EDIT:  I just realized that my monitor's Y resolution (768) is smaller than the Y resolution that I'm telling df to run at (800).  Would this result in me losing those 32 pixels on the Y axis?  Would your tileset still work okay if I lowered my resolution a bit?  Perhaps to 1280x768? I'll go try...

DOUBLEEDIT:  No dice.  Changed my init to the following:

[WINDOWEDX:1280]
[WINDOWEDY:768]
[FONT:maydayMIN.bmp]

[GRID:80:48]
[FULLGRID:105:65]

and its still having the same issue.

[forsaken1111]

I've never tried it on a HDTV output. I use a monitor that takes HDMI input and it works fine (once I adjust the default underscan) but never tried it with a TV. Might be something odd with the way windows displays on a TV

[Baron von Eptastic]

forsaken:  Its only with the mayday tileset, using DF2010 that this problem occurs. 

If I run DF2010 with the default tileset, I don't have this issue.  Or if I run 40d with the mayday tileset, there are no issues.

And just for laughs, I'll post my entire init file, just in case I'm missing something:

Spoiler (click to show/hide)

[SOUND:ON]

[VOLUME:255]

[INTRO:OFF]

[WINDOWED:PROMPT]

[WINDOWEDX:1280]
[WINDOWEDY:768]
[FONT:maydayMIN.bmp]

[FULLSCREENX:1680]
[FULLSCREENY:1050]
[FULLFONT:maydayMIN.bmp]

[BLACK_SPACE:YES]

[GRAPHICS:YES]
[GRAPHICS_WINDOWEDX:1280]
[GRAPHICS_WINDOWEDY:800]
[GRAPHICS_FONT:mayday.bmp]
[GRAPHICS_FULLSCREENX:1680]
[GRAPHICS_FULLSCREENY:1050]
[GRAPHICS_FULLFONT:mayday.bmp]
[GRAPHICS_BLACK_SPACE:YES]

[GRID:80:48]
[FULLGRID:105:65]

[PARTIAL_PRINT:YES:2]

[COMPRESSED_SAVES:YES]

[TOPMOST:NO]

[FPS:NO]

[FPS_CAP:100]

[G_FPS_CAP:50]

[VSYNC:OFF]

[TEXTURE_PARAM:NEAREST]

[PRIORITY:NORMAL]

[MOUSE:YES]

[MOUSE_PICTURE:NO]

[AUTOSAVE:NONE]
[AUTOBACKUP:NO]
[AUTOSAVE_PAUSE:NO]

[INITIAL_SAVE:NO]

[PAUSE_ON_LOAD:YES]

[EMBARK_WARNING_ALWAYS:NO]

[SHOW_EMBARK_TUNNEL:FINDER]

[TEMPERATURE:YES]
[WEATHER:YES]
[ECONOMY:YES]
[INVADERS:YES]
[CAVEINS:YES]
[ARTIFACTS:YES]
[ZERO_RENT:NO]
[TESTING_ARENA:YES]

[LOG_MAP_REJECTS:NO]

[EMBARK_RECTANGLE:4:4]

[PATH_COST:1:2:5:25]

[STORE_DIST_ITEM_DECREASE:20]
[STORE_DIST_SEED_COMBINE:1000]
[STORE_DIST_BUCKET_COMBINE:1000]
[STORE_DIST_BARREL_COMBINE:1000]
[STORE_DIST_BIN_COMBINE:1000]

[COFFIN_NO_PETS_DEFAULT:NO]

[WOUND_COLOR_NONE:7:0:1]  No recorded active wounds on the part.  Default = white
[WOUND_COLOR_MINOR:6:0:0]  Any damage that doesn't have functional/structural consequences (might be heavy bleeding though).  Default = brown
[WOUND_COLOR_INHIBITED:6:0:1]  Any muscular, structural or functional damage without total loss.  Default = yellow
[WOUND_COLOR_FUNCTION_LOSS:3:0:1]  An important function of the part is completely lost, but the part is structurally sound (or at least partially intact).  Default = bright cyan
[WOUND_COLOR_BROKEN:4:0:1]  The part has lost all structural integrity or muscular ability.  Default = bright red
[WOUND_COLOR_MISSING:0:0:1]  The part is completely gone.  Default = dark gray

[SKY:178:3:0:0]

[CHASM:250:0:0:1]

[IDLERS:TOP]

[POPULATION_CAP:200]

[BABY_CHILD_CAP:100:1000]

[VARIED_GROUND_TILES:YES]

[ENGRAVINGS_START_OBSCURED:YES]

[SHOW_IMP_QUALITY:YES]

[SHOW_FLOW_AMOUNTS:NO]

[SHOW_ALL_HISTORY_IN_DWARF_MODE:YES]

[KEY_HOLD_MS:150]

[RECENTER_INTERFACE_SHUTDOWN_MS:0]

[MORE:YES]
[DISPLAY_LENGTH:23]

[ADVENTURER_TRAPS:NO]

[ADVENTURER_ALWAYS_CENTER:YES]

[ADVENTURER_Z_VIEWS:UNHIDDEN:9]

[NICKNAME_DWARF:REPLACE_FIRST]
[NICKNAME_ADVENTURE:REPLACE_FIRST]
[NICKNAME_LEGENDS:REPLACE_FIRST]

[BLACK_R:0]
[BLACK_G:0]
[BLACK_B:0]

[BLUE_R:30]
[BLUE_G:50]
[BLUE_B:168]

[GREEN_R:96]
[GREEN_G:170]
[GREEN_B:0]

[CYAN_R:0]
[CYAN_G:128]
[CYAN_B:140]

[RED_R:200]
[RED_G:20]
[RED_B:0]

[MAGENTA_R:128]
[MAGENTA_G:50]
[MAGENTA_B:200]

[BROWN_R:140]
[BROWN_G:98]
[BROWN_B:56]

[LGRAY_R:192]
[LGRAY_G:192]
[LGRAY_B:192]

[DGRAY_R:128]
[DGRAY_G:128]
[DGRAY_B:128]

[LBLUE_R:0]
[LBLUE_G:120]
[LBLUE_B:255]

[LGREEN_R:134]
[LGREEN_G:213]
[LGREEN_B:0]

[LCYAN_R:0]
[LCYAN_G:200]
[LCYAN_B:255]

[LRED_R:255]
[LRED_G:50]
[LRED_B:0]

[LMAGENTA_R:210]
[LMAGENTA_G:10]
[LMAGENTA_B:255]

[YELLOW_R:255]
[YELLOW_G:232]
[YELLOW_B:76]

[WHITE_R:255]
[WHITE_G:250]
[WHITE_B:230]

Again, thanks for the help everyone!  I appreciate it.

[Mike Mayday]

The settings you need to edit are
[GRAPHICS_WINDOWEDX:1280]
[GRAPHICS_WINDOWEDY:800]

Since (I assume) you play with gfx on, right?

[Baron von Eptastic]

That did it.  Thanks Mayday!  Cripes.  I feel dumb.

[blinking icons]

The game seems to run fine on my machine with mayday and 1024x768 resolution (windowed). There is the tinyest little-est bit of graphics corruption in the top line of the window, but fps and idlers are displayed correctly. Should I expect any other problems to show later??

If not, I would recommend you tone down the statement about 1280 to smth like "you can try lower res, but..". I just spent hours getting used to that horrible resolution but in the end I had to switch back and then tried DF mayday with changing the resolution in the init and - yay!

[Mike Mayday]

I'm glad you find it acceptable but it is a solution I don't wish to support in any way.