Home   Help Search Login Register  

Author Topic: Another problem.. so soon from last  (Read 1282 times)

0 Members and 1 Guest are viewing this topic.

Offline JasonO

  • OFPEC Patron
  • ****
  • Oh no...
    • The New Life RPG
Another problem.. so soon from last
« on: 03 Sep 2006, 16:56:29 »
Hi

OK When I click an action on a flag pole an error apears. The weird thing is.. is that the line it refers to isnt in my script anywhere.



Thats the error message I get, but that line I cannot find in my script. I have written all the scripts so far by hand, and I know I defnitly havnt added it.

Thanks for your help  :) (again)

EDIT: I fixed it! For some reason in my script it didnt like that I wanted to wait 0.1 before continuing (using ~0.1) so I changed the number to 0.11 and its fixed. Why wont it let me do 0.1 ?

Offline Trapper

  • Honoured Contributor
  • ***
  • I'm a llama!
Re: Another problem.. so soon from last
« Reply #1 on: 03 Sep 2006, 17:03:57 »
Oh you have added it somewhere yourself, trust me.   8)

I would open all files including mission.sqm with notepad and search them for __waituntil.


EDIT:
Quote
Why wont it let me do 0.1?
Looks like it was 0.| or 0.l and not 0.1

Offline JasonO

  • OFPEC Patron
  • ****
  • Oh no...
    • The New Life RPG
Re: Another problem.. so soon from last
« Reply #2 on: 03 Sep 2006, 17:04:59 »
Oh you have added it somewhere yourself, trust me.   8)

I would open all files including mission.sqm with notepad and search them for __waituntil.

Read first post, I edited it.

I think __waittime is used in the game engine, because like I said the line dosent exist in my mission and when i changed ~0.1 to ~0.11 it fixed it  :scratch:

Offline Trapper

  • Honoured Contributor
  • ***
  • I'm a llama!
Re: Another problem.. so soon from last
« Reply #3 on: 03 Sep 2006, 17:10:13 »
Yes, ok. Please read second post again, too. :)

Btw I'm wondering why you're writing __waituntil and not just _waituntil. Makes no sense to me as one _ already makes it a local variable.

Offline JasonO

  • OFPEC Patron
  • ****
  • Oh no...
    • The New Life RPG
Re: Another problem.. so soon from last
« Reply #4 on: 03 Sep 2006, 17:13:48 »
Yes, ok. Please read second post again, too. :)

Btw I'm wondering why you're writing __waituntil and not just _waituntil. Makes no sense to me as one _ already makes it a local variable.

I dont think you understand... __waituntil is not in my script at all. Ive checked all my scripts and mission.sqm and its not there. I am very certain its a line used in the OFP game engine. My script had a ~0.1 pause.. and thats where the error was created. Now I have change the ~0.1 to ~0.11 it works, and no error apears.

I am just wondering why I got an error and reason why I cant use 0.1 as a script pause time.

Offline bedges

  • Administrator
  • *****
    • OFPEC The Editing Center
Re: Another problem.. so soon from last
« Reply #5 on: 03 Sep 2006, 17:18:09 »
it looks like an L to me, rather than a 1, but that could be the pic. make it 0.1 and check again...

and i too have experienced something similar to this, and it does come from the game engine, so you're not losing your mind ;)

Offline JasonO

  • OFPEC Patron
  • ****
  • Oh no...
    • The New Life RPG
Re: Another problem.. so soon from last
« Reply #6 on: 03 Sep 2006, 17:21:21 »
I changed it back and its fixed.

Didnt think the OFP engine had script errors like these.

Ahhh well bedges answered my question for if im mad in the head or now... and results are good.

Thanks for your answers guys ;)

Offline bedges

  • Administrator
  • *****
    • OFPEC The Editing Center
Re: Another problem.. so soon from last
« Reply #7 on: 03 Sep 2006, 17:43:08 »
to be strictly accurate, the error was not in the game engine code, the error was generated by the engine trying to wait 0.L seconds.

Offline Planck

  • Honoured
  • Former Staff
  • ****
  • I'm never wrong ....I'm just not always right !
Re: Another problem.. so soon from last
« Reply #8 on: 03 Sep 2006, 17:49:13 »
And..........

~ actually means __waituntil as far as the game engine is concerned.
When the engine encounters ~ it reads __waituntil.

It is a reserved variable and should not be used by us.


Planck
I know a little about a lot, and a lot about a little.