Problem with object scripting.

iamdaman13
Sometimes I have this problem with scripts: I'll create some object, let's say a "table". I'll give it a script whenever examined it makes an object on it accessible. I'll make another object in another room, let's say an "apple". I'll go to where I can add scripting for when you examine this object, but for some strange reason it will have the script I created for "table". So I'll remove it and type in the scripting for the "apple". I'll go back and check the scripting on the "table" and it has been erased and replaced with the "apple" script.
To make better sense, I'll simplify what I described. Sometimes when I edit scripting on an object, it seems to be linked to the scripting of another object and changes that objects script to match the one for the first object. I've found ways to fix this, but it's way too tedious. Does anyone know what's wrong and how to fix this problem? Thanks.

Farvardin
if you have this problem in QDK, is it for the last version of Quest ?
I've never had this kind of problem before. Could you eventually send me your *.asl file, and I'll test it on my system.
Have your ever tried to edit this tedious part with a text editor instead ?
Generally I find it quicker to use QDK pleasant features to create the skeleton of a game, add the main scripts, descriptions and such, and finish to edit the game by hand

Alex
Thanks for reporting this. Strangely the script only appears when you click the Edit button. I'm not sure why this is happening, but I'll take a look into it and post a fix shortly.

Alex
I've now fixed this problem and you can download an updated QDK.EXE. Start QDK, go to the Help menu and click "Check for Updates".

iamdaman13
It seems that the link is still downloading build 3.5.122 instead of 3.5.123.

Anonymous
Hi Alex

Any chance of us registered users of Quest Pro getting our 'password to download' e-mails for this fix?

Al (MaDbRiT)

Anonymous
Hi (again) Alex

D'oh... ignore the above - it's the same password as the last one isn't it.

Excuse me - Brain in neutral this morning. :-(

Al (MaDbRiT)

Anonymous
... except that it doesn't work.

Trying to use the QDK check for updates followed by e-mail address & password just downloads me a zero-byte file.

Any suggestions?

Al (MaDbRiT)

Alex
I don't know why it wouldn't be working - if you were able to download Quest Pro 3.51 you should be able to download the update. If it's some kind of AOL thing, did you download Quest Pro 3.51 via AOL or did you start up a separate Internet Explorer? If you try the same method for the update (it's at http://www.axeuk.com/quest/pro/index2.htm ) you should be able to download it.

Anonymous
Hi Alex

Bizarre result. Trying online, by opening a separate IE window outside AOL causes the zero byte file download (suffix 'nopwd' to the URL = no password i assume), opening it within AOL's custom IE browser causes the same problem. On both occasions my download manager software kicks in and I get nothing usable.

However, closing AOL completely, then using the 'check for updates' in QDK opens AOL & logs on, then opens the page within AOL's browser and downloads the file - somehow bypassing the download manager software & giving me the standard IE download a file dialog - which then seems to work just fine!

Presumably this means that the problem lies with my download manager software - which is odd because I've been using it for years and haven't updated it in several months. I must have done SOMETHING differently this time - because I'm sure (my log tells me) the download manager was used to download Q3.5 & the previous beta.

One of 'those things' I suppose.

Al (MaDbRiT)

Alex
Yes, sounds like a download manager issue to me. It sounds like it was intercepting the form post which contained the username and password, and trying to request the zip file separately. However it then didn't send the username and password, so it got redirected back to the login page with the ?nopwd suffix. This sounds like rather bad download manager design to me - perhaps there's an updated version that fixes the issue?

This topic is now closed. Topics are closed after 60 days of inactivity.

Support

Forums