Well, it's been awhile since I've worked on my game, but I stopped by and saw there was a newer version available and downloaded it (4.04). I opened the new QDK and ran my game to find out that I'm getting a Runtime Error all of a sudden right at the beginning. It is Runtime Error 35601 Element not found. I've never gotten this before.

...Ugh!... so I thought I'd click the Toggle View Code button so I could copy and paste the code where I'm having the Error occur, but all that happens is the program freezes up and doesn't respond. So I have to close the program.

So, anyways, I opened WordPad and copied the area where it gives Runtime Error: (When player enters name and presses enter, the pop-up box with Runtime Error displays. I double-checked and played the beep_2.WAV file to make sure that wasn't corrupt because the noise doesn't occur. So I'm guessing it has to do with #Player_Name#)

define room <UAGAN Set-Up Part One>
	alias <UAGAN Set-Up>
	description {
		clear
		msg <|n|jlHello traveler.  Welcome to your Zanzibari vacation.  I'm UAGAN.  UAGAN is an acronym for Updatable Adventure Guide And Narrator.  As my name suggests, I will provide guidance and narration for your adventurous vacation.  I'm updatable too, so take advantage of my add-ons that you'll find along the way.|n|n>
		wait <|crPress a key to continue....|cb>
		msg <|n|nSo I can customize my guidance and narration program to conform to your identity, please type your name into the text entry box, which is located underneath the main text window, then press enter.|n>
		msg <Name:  |xn>
		enter <Player_Name>
		pause <1000>
		msg <#Player_Name#>
		playwav <beep_2.WAV>
		pause <1000>

Then I went to Run the game again, because I remembered about the Debugging option in the drop down box in the Quest Game Player, but all I get is WordPad opening up now when I press the Launch Game button. So, in other words, now my game won't open up.

I'm using Vista.

Any help would be greatly appreciated.

can you upload the game here? so that i can try to run it my self.

I attached the ASL file with the first three WAV files used in the game (WAV files are not allowed as attachments, so I guess all you're getting is the asl file). That should be enough for you to see what I'm experiencing (which might not be true anymore, since I'm not sure if you'll experience an error when the game attempts to find the appropriate WAV file).

Ok. Delete that. QDK 4.04 does not allow capital letters to be used in a string name. Which means I'm going to have to go and waste time editing this in all my string names. Alex, why oh why did you goof with this?

Is anyone else experiencing freezing with the Toggle button freezing the screen (not responding)?

--update--> It goes thru a Not Responding spiel for about 10-15 secs. as if QDK is frozen up, and then goes back to normal with the text ASL file opening up in the editor. (This is obviously not right; any ideas?)

Now my game won't launch when I press the Launch Game button. All that happens is that WordPad opens up and shows my text ASL file. Any reason for this?

This is still happening. The only way I can play a game is to go thru my C: drive and right click on the asl file and "Open with" Quest 4. How do I re-associate QDK with QuestPro?

I'm not seeing any attachments. Can you please attach (or email) the file so I can reproduce the problem?

The "View ASL" feature can be a bit slow with large games. The performance is better in QDK 4.1.

To make Quest launch properly for ASL files, start Quest, then click Tools, Options, Other, then the "Restore File Associations" button at the bottom.

It would help if you could attach the file so I can fix the bug in QDK which causes the run-time error with upper-case string variable names, as these should work properly..

Not sure why the Restore File Associations isn't working - maybe try right-clicking Quest Pro in your Start Menu, choose "Run as administrator" and try again? It might need admin privileges to make the required change to the registry.

It would help if you could attach the file so I can fix the bug in QDK which causes the run-time error with upper-case string variable names, as these should work properly.

Hmmm. I wrote a simple code to input text into a string name with capital letters then have it printed out to mock my code, and I didn't get a Run Time Error. But when I try it with my game-code, I still get the Runtime Error when string name is capped. I'm not sure why. My code got all messed up when I wasn't aware of the abbreviated commands were allowed and couldn't figure out why I was getting problems. So if you get a bit confused in why I'm working code one way, and another some other places. That is why. Then when you placed the option to choose if abbreviated commands are allowed, I kind of got perturbed with half of my code going one way while half of it was still in the old form, and gave up in my confusion of what the hell I was doing. I've attached my game again. But just the asl, without sounds and graphics.

Not sure why the Restore File Associations isn't working - maybe try right-clicking Quest Pro in your Start Menu, choose "Run as administrator" and try again? It might need admin privileges to make the required change to the registry.[/quote]

Tried this. Nothing happened. Still get text ASL when I click Launch Game button.

Long time no see witch!

(Yeah, I'm offtopic and unhelpful. Sue me)

Hey Thanatos. Yah, it's been awhile. Thanks for the greet. Sorry, I remember your handle, but did we get into some conversations. If so, give me a keyword ot two to remember you by. No disrespect meant.

eh... I haven't a clue, friend. The only time I can ever remember being in the same thread as you would be when Michael the Gamer was still around (:lol:)

Hah! I thought of him after I read your post. That must be why. Did he ever end up getting along with anyone or did he continue to yell about getting bad reviews by DavidW on his game? I remember trying to tame him, and he seemed to calm down a bit afterwards.

What was your avatar then? I know it wasn't what you have now.

I didn't search the forum's past posts, but I seem to remember helping you on how to do some random thing with a pond and fishes. Was that you?

Michael? He still roams the site, but he tends to get on sort of well with me now. Looks like im an 'ally' now

Oh god. I have no clue what my avatar was then - I change it frequently. But ima stick with this one from now on.

And nope, that wasn't me

Well... that was a waste of time.

Sharing a friendly greeting is never a waste of time

Thanatos, I wasn't referring to you. I was referring to posting my code for Alex to look at. I did so last Saturday and I haven't gotten a response back.

Ouch...

I go through this everytime there's an update. It really discourages me from finishing my game, and it's been a dream of mine since about 22 years ago when I was in 7th or 8th grade trying to learn Basic. I want to finish this game, but the QDK issues and response time is starting to destroy my happiness. The problem is that I get in the mood to work on the game, a problem arises, and then by the time someone gets back to me or it's solved, I'm on to recording music or writing a book or something else. And it always seems I'm the only one who experiences the problems I do, so some special magical remedy has to be discovered and applied. Why do you think v4.02 (i think it was) added the option to turn off or on abbreviated commands? Yep. That was me. I couldn't figure out why I was getting a conflict when I'd type in "get screw". Well... there was a "screwdriver" also. Quest couldn't discern the difference between the "s-c-r-e-w" and the "s-c-r-e-w-driver". So, because I thought I goofed up, I started reworking my code in a new way, and found out in the end it wasn't my coding. By that time, my brain was forgetting what did what and which way it did whatever it was trying to do. Hell, I don't even know where the new code ends and the old code starts. And I was like half way done with my game, and it's getting fairly big. Oh well. So I urged and urged Alex to put the option to turn on or off abbreviated commands, and he did, and I'm thankful for that! I always thought abbreviated commands were getting out of hand and just made the player lazy anyhow. "get cr" or "move te" is just a bunch of garbage, and makes the game less realistic. Hey Thanatos! "How yo d go? Mi is fi." Lol!

o_o

Yeah, quest is a bitch.

hats whyI don't code! Wheeeeee...

Sorry for the delay, but I thought you had a workaround for the issue?

Forums are probably not the best place to log issues that definitely require a response, as they can easily get lost. For now I suggest sending me an email if there's a problem that's stopping you from continuing. I can't promise to fix issues instantly - this is not my full-time job after all - but I'll do the best I can.

I'm taking a look into setting up Bugzilla so we'll have some proper bug tracking.

I've run into the CaSe SenSiTiVe bug a couple of times in the past - which is why I do EVERYTHING in lowercase for Quest now.

This has been in effect since version 2.80 - or thereabouts.

I don't actually recall abbreviations actually working in the first place for me..
For example:
command <kick #@object#> msg <You kick the #@object#>

Would never work if I had the object "ball" in the room and typed: "kick ba" ... it'd just complain that no object called "ba" was there.

The problem, Paul_One, is that the capitalization works in 4.02 but not 4.03. And for some reason when I press the Game Launch button WordPad opens with my ASL code rather than opening Quest Pro. If you read the thread you'll see I've followed Alex's rule to reset the connection, but that didn't work either. I've never had these problems before. Can you help me?

I've had no problems with capitals in 3.53, as for my engine all variables start 'EE.' and work fine.

._.

See, this is why all I do is write descriptions

I'm not sure how close windows vista is to XP, BUT:
In the folder you've got the ASL file:
shift and right click the file, and select "open with...".
Open with the Quest application and tick the box "always open with this application".

... You may get prompted with loads of UAC prompts (or not).

Another way is to also go into the folder, go into the tools menu, options (I think).
Where you can browse the "file types" and set in there how the files are opened.

Again, I'm going from a Windows XP/98 *memory* here - and I can't be bothered to look up walkthroughs on google for you.
So you may need to actually think about my response and interpret - instead of blindly following.

The problem, Paul_One, is that the capitalization works in 4.02 but not 4.03

Ture - it is a bug that has been introduced - BUT I would none the less say that the 'problem' is that the variables and any code parts/names/menus/functions, should all be in lowercase, since Quest has a history of not fully working with case insensitivity ("Define Game" didn't used to work, along with some "End Define"s - don't know if that's fixed or not, I'm sure I've run across others)

That is almost like saying "well spaces weren't taken out of strings in version 4.3 - but they are now", when Quest has 99% of the time removed leading/trailing spaces from strings.

paul_one

Did you hack into my computer and reset how ASL files are opened? Because I didn't do anything except go into the folder, click on the game to select it, select the "open" button at the top (Vista), scroll down, and open a box where Quest was already selected as program to open ASL files with.

Whatever, I thought. I opened QDK, hit the Launch Game button, and my game opened up in Quest Pro. Woohoo!

It was pretty cool to see that I can associate files that way though in Vista. Thanks for the lesson (and the hack?).

(Damn it! I liked using upper-case though, since it visually separated them from other things I use lower case for. But I'd rather not have the headache. But, then again, I'd rather not have to edit all this effin' code either).

Find & Replace my friend...... Find & replace..