Annoying Error Message, ALWAYS (Quest 5.2)

FilozofTM
26 Aug 2012, 06:42
I am always getting annoying error message, even if i didn't do&modify anything in game, just create it.

Using Quest 5.2.

1. Step- Start Quest
2. Step- Create New Game
3. Step- Give it a name, (Ronald, FilozofTM, or tutorial game)
4. Step- Waiting it to load, (1-2 seconds)
5. Step- Pressing F5


And i get this:

Error running script: Error compiling expression 'IsDefined("oldRoom")': SyntaxError: Unexpected character: I Line: 1, Column: 1 




Is there anything i passed out? Is creating game in Quest is not as easy at it seems, or you told? :(

Any help would be appreciate.

(Tried on 3 computers, 2 with Windows 7 Ultimate 64 bit, the other with Windows XP SP3 32 Bit. Still nothing worked.

Specs of computers,

i5 2500K, 2 6850's, 8 Gigs of 1600 MHz Ram v.s v.s

second computer(laptop) AMD Trinity A6-4400M, HD7670M, v6 Gigs of Ram

And the third one is very old one, Celeron M and Intel HD910 Express with 1.2 Gigs of Ram.

cdutton184
26 Aug 2012, 11:30
I've just tried Ronald Game.aslx on my Quest 5.2 and it works fine (followed exactly what you did).

Try and reinstall Quest 5.2 from this site and if it still doesn't work then it must be your computer.

Pertex
26 Aug 2012, 11:31
This is strange! I don't have that problems here, not with a new created game nor your appended gamefiles

Alex
26 Aug 2012, 13:30
I see you are based in Turkey, and it looks like there's a bug in FLEE (which Quest uses to compile expressions) - http://flee.codeplex.com/discussions/265251

Quest has its own fork of FLEE at https://bitbucket.org/alexwarren/flee so I will see if I can fix this bug myself (unless anybody else fancies a go at it)

In the meantime you might be able to get it to work by temporarily changing your Windows regional settings to something else like US English.

FilozofTM
26 Aug 2012, 15:24
Thank for response guys.
Yep, in Turkey. Must be a FLEE problem, but i don't think it would got high priority, so thanks again.

Alex
09 Nov 2012, 18:16
I have now fixed this in FLEE and checked this in as a fix for Quest 5.3.