Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Vaunted

#1
Quote from: Crimson Wizard on Thu 10/10/2013 10:56:47
This is something unexpected. Do you use the latest beta version (#8)?
Ack! I checked this before I posted, but I somehow goofed anyway. You're right, I was a couple betas behind. Running it with Multiplied Translucense in beta8 works properly. Thanks, and sorry to have made such a silly mistake.
#2
Thanks for all the work on this. It's something I was struggling with in older builds, specifically with GUI buttons, and 3.3.0 has fixed a LOT of my problems. I'm still getting some weird issues with alpha blending, however. Specifically, if I use png buttons with alpha transparency in a GUI with a transparent background (bg image and color both 0) using the Multiplied Translucence setting, it leaves a 1-pixel wide faint pink border around each sprite.

(Those left and right arrows are their own images, however, and I notice that THEY don't have a weird border where they blend onto the image behind them.)



I've tried setting the background image to a fully transparent image rather than leaving it as 0, but it just makes the phantom border a deeper shade of pink.

I've also tried using additive opacity instead, and actually does seem to solve the pink border issue! However, it seems to break in the opposite direction, drawing properly onto GUIs with transparent bgs but turning things with an alpha channel drawn onto another image (but only within the same GUI?) into a hideous blob.


Sorry if this is a known issue in the beta, I couldn't find this precise issue being discussed (although it's possible I did and I just didn't understand).

edit: Fixed some erroneous information, forgot how I had the images in the GUI set up. Sorry.
#3
Terrific, thanks Khris! That's a huge help.
#4
Sorry if this has been answered or covered elsewhere, I searched around for a while and couldn't find anything precisely like this.

I'm finding that if I leave an inventory item's cursor hotspot set to the default of 0,0, AGS ignores that setting and places the cursor hotspot in the middle of the item's cursor image. If I manually set the cursor hotspot to 1,1 in the inventory item's settings, however, it works as expected. I realize I could just go through my inventory items and manually set all the cursor hotspots to 1,1 rather than 0,0 as a workaround, but I'm curious if this is just a quirk of the engine or something I've caused somehow. All the other cursors -- ie., the ones not derived from an invitem -- work just fine with 0,0 for the hotspot.

The only other relevant bit of info I can think of is that I'm using a standardized item cursor image that's the same for every item, because I'm highlighting the currently selected inventory item in the inventory window rather than using the cursor to indicate which item is selected. The code for that isn't actually implemented yet, though, so I can't see how it'd have any effect.

I've read in older posts that AGS will ignore the cursor hotspot if it's set for an x,y that's located outside of the image (like -10, 2), but I don't see why 0,0 would be acceptable for non-InvItem cursors but not for InvItems, unless they're just arbitrarily different and/or handle the exception differently.
SMF spam blocked by CleanTalk