Home   Help Search Login Register  

Advertisement

Author Topic: SQF debugging  (Read 1373 times)

0 Members and 1 Guest are viewing this topic.

Offline SoldierEPilot

  • Members
  • *
SQF debugging
« on: 17 Apr 2015, 10:41:05 »
Scripters of OFPEC, how do you think, what the OFP debugger
wants to tell me with these strange symbols in the start of error message ???
« Last Edit: 19 May 2015, 17:43:32 by SoldierEPilot »

Offline h-

  • OFPEC Site
  • Administrator
  • *****
  • Formerly HateR_Kint
    • OFPEC
Re: SQF debugging
« Reply #1 on: 17 Apr 2015, 15:09:18 »
Ah, the awesome one-liner error printout..  :clap:

Have you checked the script file isn't .rtf (or any other non-txt file)?

Also, if you're running CWA it has it's own .rpt file so that might show the full error message (non-steam installed version has it in it's root folder)..
Project MCAR   ---   Northern Fronts   ---   Emitter 3Ditor
INFORMATIVE THREAD TITLES PLEASE. "PLEASE HELP" IS NOT ONE..
Chuck Norris can divide by zero.

Offline Wiineri

  • Members
  • *
Re: SQF debugging
« Reply #2 on: 17 Apr 2015, 21:09:34 »
Well, I think that the error message seems to imply that there are unknown characters in the beginning of the file. Could you upload the whole sqf-file? Without seeing the file itself, it's hard to figure out what's wrong with it.

Offline SoldierEPilot

  • Members
  • *
Re: SQF debugging
« Reply #3 on: 17 Apr 2015, 21:31:55 »
Quote
unknown characters in the beginning of the file

@Wiineri, @h-, thx 4 ideas and fast response.
I thought that can be the reason of such a start sequence in file,
checked encoding and (yesss!) it was UTF-8 encoding feature.
I just decoded source file  into ANSI, now all works just fine.

P.S. Source file is not worth to see - fat, indigestible, spaghetti-code :D


Offline Wiineri

  • Members
  • *
Re: SQF debugging
« Reply #4 on: 17 Apr 2015, 22:44:28 »
You're welcome.

Quote
Source file is not worth to see

Yeah, not necessary to see it now that the problem is solved. But it usually is a lot easier to find the problem, when one is able to actually run the code.