AGS 3.0: Your feedback would be appreciated

[monkey0506]

Oh -is there a button I'm missing that will jump me right to the room script, instead of having to click the interaction lighting bolt and then a random interaction (i.e. the old "{ }" button)?

When you expand the room item you will see "Room script" which you can double-click to open: Room->#: DESC->Room script (# is room number, DESC being the room's description).

[Baron]

Ah, you know I've actually done that several times, but I still instinctively look for the button  : .

[Ishmael]

I'm with BaRoN on the issue of the extra clicks related to view spriting and such options. Too much clicking to be done :\

[NiksterG]

I think the new editor is great. Though it does have a few extra clicks in some places, that really helps the organization, in my opinion.

Just give the editor a chance. After a while, those few little things that bug you at first vanish.
The greatest force in the universe is human resistance to change. 

[Ishmael]

The greatest force in the universe is human resistance to change. 

I don't resist change for the better. There just are certain things that used to be better than they are now, in my opinion.

[Galen]

More clicks for adding sprites for a character? Impossible. :

[Pumaman]

Alright I've used 3.0 for all the basic things, and overall I must say I like the new format, especially the tabs.  There are a few areas where I find it a bit slower than previous versions (other than the one mentioned above):

Thanks for your feedback, it's really useful. I'll see what I can do.

I seem to remember the old version letting you select options from a list, which was great. Now it seems you have to manually type into the scripts themselves, which may not seem a great problem to experienced people. But to a beginner who just want's to try to get a few rooms together it is rather intimidating, and offputting.

I appreciate this, but actually the old interaction editor wasn't that friendly. To display a message you had to create a "Display message" interaction from the menu, then create a global/local message, then set the text, then link up the message numbers. I think it gave an illusion of ease which doesn't necessarily reflect the reality.

The equivalent script for the simple things that the interaction editor supported (like displaying a message) is quite simple so hopefully people can get into it fairly quickly and not be scared of scripting.

the baseline tool, is it gone or just hidden

Yeah, that is gone, and I can appreciate typing a number in isn't an improvement over selecting it graphically. I'm not sure if there'll be time to bring it back for 3.0 though.

Imported a sample from 2.72 and it looks like a row of pixels is missing in my dialogs first row, whatever the first row may be. Had no problems with that in 2.72.
Problem dissapears when I disable "Use GUI for dialog options".

I've looked into this, it's due to game.dialog_options_y being set to -2, and 3.0 doesn't work properly if you use a negative number for the dialog_options_x/y. I'll get it fixed.

[Rincew1nd]

I retract this message, my liking with 3.0 has improved.

[Galen]

Since I can't be bothered downloading to check one feature.
But in 2.72 there was an option to pop up  a GUI if the mouse was above a certain y coordinate. This should be usable for "bottom-GUIs" aswell (if I'm missing something, beat me up or something).

Teeny possibly redundant or already implemented suggestions aside, easing out case-sensitivity might be a wise decision for the future, it would avoid alot of stupid errors and typing time, I can't think of any negative reason at the moment.

[Ishmael]

Teeny possibly redundant or already implemented suggestions aside, easing out case-sensitivity might be a wise decision for the future, it would avoid alot of stupid errors and typing time, I can't think of any negative reason at the moment.

The autocomplete is there for a reason, and without case sensitivity both it would be lost, and soon you might be lost in your code.

[Galen]

If the autocomplete didn't work then it would obviously not be entirely case-unsensitive.

[Ghost]

Okay, I have worked now for a while with RC4 and 2.72 in comparison. A lot of things that I considered to be "bugs" were actually errors or warnings that cropped up because I was set in my 2.72 ways, and did things "wrong" in RC4.

It works nice. The extender functions are a great addition, and after getting used to the new debugger/exe functionality, it was also very useful. It is true that there is some "getting used to" involved, but I think it's mostly for the better.

I can live with the additional clicks and I can totally live with the absence of the Interaction Editor (I always only used to to make "run script" anyway).

What nags me are two purely cosmetical things. I totally understand if the are never included.
1) I *hate* the crosshair selction for hotspots. It just was so much more convenient to have an actual "pixel square" marking the hotspot of cursors and inventory items.
2) Could we have a "remember outlay" feature? Each time I launch RC4 the tree and settings windows are reset to their default states, and I need to enlarge the tree view a good deal to have all entries visible (You may remember I'm one of those old-fashioned 800x600 users).

Apart from that, and I said so before, the new look's great, the added functionality totally functional, and the new templates (Rui's extended Default and Elektro's Verb Coin) just the icing on the cake.

[Gilbert]

Teeny possibly redundant or already implemented suggestions aside, easing out case-sensitivity might be a wise decision for the future, it would avoid alot of stupid errors and typing time, I can't think of any negative reason at the moment.

It can be considered a large change though, as removing case sensitiveness would possibly break stuff in projects started with earlier versions (among which inevitably saying good-bye to old string compatibilities and mouse/Mouse, etc.). So it should be included in a HUGE update version instead, that means people working with a game with a previous version of AGS are not advised to upgrade (unless they're experienced users who are ready to make changes).

I didn't say V3.0 was not a huge update, but V3.0 focuses mainly on the new editor, most part of old projects should still work after the update.

[Galen]

Possibly, it has always just felt a bit outdated and overly stringent (I break up words in variables with underscores so it's "big_gas_tank" instead of "BigGasTank" in other languages), plus I just find it alot faster to process, but
I guess if noone else is overly bothered then I can live with it.

[Monsieur OUXX]

I think it is absolutely essential that the install wizard detects if .NET framework 2.0 is installed or not.

I had the issue (I had installed it previously but it had been disabled by some development tool that I had installed), a friend of mine had the issue, and also a friend of my friend
--> everytime you say "hey, give a try to AGS, it's great" the other person answers "I tried it but it crashed at startup for some random DLL reason"

[goldensox]

Well, i guess that one of the most wanted tools for it is the Eraser for the room hotspots, so then we dont have to erase the whole hotspot if we fuck a little pixel out

[DoorKnobHandle]

Use Color 0.

[goldensox]

Use Color 0.

thankz for helping unn00bing me >.>

[goldensox]

also, why the fuck theres no more support of the .PCX format? it will be a pain in the ass to convert all that content...

[Ghost]

No moderator, me, but: Easy on the f word.

AGS has lost pcx but gained other, probably more versatile formats. And there are programs out there that can auto-convert whole batches of files with a mere two clicks.