
A few minor b34 bugs
Moderator: Moderator
-
- Yeek
- Posts: 14
- Joined: Thu Nov 11, 2010 3:12 am
- Location: Trail, OR, U.S.A.
A few minor b34 bugs
Well, these are all pretty minor but I figured I'd post them anyway since I couldn't find any other threads regarding these problems. First of all, ever since downloading b32 or 33 (forgot which, but seems like it was b32) I get a message about changing the resolution every time I load the program and get to the main menu (new game, load game, etc...) and I have to click "accept" to make it adjust to fullscreen correctly before re-loading the main menu screen. It's a minor, yet somewhat bothersome problem that wasn't there before so I thought i'd mention it. Secondly, I've noticed a small graphical error in the abashed expanse which has been there at least as far back as b31 and still remains the same in b34. I've attached a screenshot of it. Also, if you copy the picture as a file and open it with paint and stretch it by 200% both horizontally and vertically it will then be the same size it was when T-engine saved it. I had to shrink it by 50% horiz/vert to make the file small enough to attach
. But anyway, if you look at it closely you will see that the tiles outside of my LoS are just darker, but not actually transparent. Srry bout that, next time i'll leave it at full size and just post it on imageshack or someplace.

- Attachments
-
- Screenshot of Abashed Expanse Very Minor Graphical Error
- tome-3.9.34-1316679587(1).png (249.08 KiB) Viewed 1005 times
Last edited by GodSlayerX on Fri Sep 23, 2011 1:35 am, edited 1 time in total.
Re: A few minor b34 bugs
Nice screenshot! When "Smooth fog of war" graphical option is disabled, the brightness/darkness is set by modifying the alpha channel (i.e., transparency). This looks ugly in a lot of places, but it looks mostly fine in normal dungeons. The Abashed Expanse has a background image, though, so the transparency of the unseen tiles does more than set the "brightness" of a tile: it lets you see the background. I've gotta ask, though: why aren't you playing with "Smooth fog of war" enabled?!GodSlayerX wrote:Secondly, I've noticed a small graphical error in the abashed expanse which has been there at least as far back as b31 and still remains the same in b34. I've attached a screenshot of it.

-
- Yeek
- Posts: 14
- Joined: Thu Nov 11, 2010 3:12 am
- Location: Trail, OR, U.S.A.
Re: A few minor b34 bugs
Hmm? Smooth Fog of War IS enabled as always. I was just trying to point out those little pieces of ground tiles that are just hovering there on the bottom-left corner and the top-right corner of the landmass in the center of the picture (the landmass my char is standing on). Also, when I click the message log button it sometimes brings it up in a really small window and then goes away real fast, alot of times it'll do this a few times in a row and then work fine for awhile. That's another wierd little thing this game has been doing to me for a few betas now, forgot to mention it earlier so.
-
- Yeek
- Posts: 14
- Joined: Thu Nov 11, 2010 3:12 am
- Location: Trail, OR, U.S.A.
Re: A few minor b34 bugs
Ok, so this one is a real pain... As of B34 I've been playing a fighter that uses 1H weapons and shields, but I've also been using bows on weapon switch. This is really the first time i've made a char that utilizes the weapon switch command. Anyway, when I right click on something, it'll randomly switch to my other weapon set as if I hit "x". This happens at random but pretty often and has almost gotten me killed a couple of times, usually when I switch to my bow with "x" and then right-click an enemy to "shoot" but instead of bringing up the list of actions (move to, attack, shoot, etc...) it just switches back to my 1H and shield wasting a turn, well really 2 turns because if I used a turn to switch to the bow but never got to "shoot" it because it just switched back to my 1H & Shld then there was no point ever switching to the bow in the first place. I checked my keybindings and "x" is the only key bound to weapon switch. I'm assuming this must be a bug, not sure if this was here before b34, if so I must have missed it somehow.