FSM Editor Problem

[JamesF1]

I'm having a small issue with the FSM Editor - it won't save Compiled FSMs.  Now, before anyone asks, I've not installed the tools drive (for various reasons), but I can happily save to the other format and it finds the compiler fine (i.e. it gets output).

The problem seems to be more related to the compiler itself, as the only output the FSM Editor gets back from it seems to be the regular 'help' information if you run the compiler without any parameters, i.e.:

Code: [Select]

FSMCompiler.exe (ver. 1.1) usage:
  Compile:
    FSMCompiler [-n] [filename.bifsm|-stdin] [-o filename2|-stdout]
  Decompile:
    FSMCompiler -d filename|-stdin -f fsmName
               [-c config.cfg] [-o filename.bifsm|-stdout]
  List FSM from file:
    FSMCompiler -l filename|-stdin
List of parameters:
 -d      decompile                     -n      get only compilation report
 -stdin  compile/decompile from stdin  -stdout compile/decompile to stdout
 -c file specify compileConfig         -o file output file
 -l file list all FSMs from file       -f name specify FSM name
 -nocompile not compile through any compileConfig
The same behaviour is found with compiling with F7...

This behaviour is not just limited to compiling, but also to decompiling... I can't open other compiled FSM's, even though they were created with 'process' set to 1 in the ScriptedFSM.cfg.

Any help greatly appreciated 

[i0n0s]

Have you set a compileConfig?

[JamesF1]

Yup, I set it to ScriptedFSM.cfg.

[i0n0s]

Hmm, no idea

[JamesF1]

Right, found some weird behaviour.  If I save the FSM to my desired directory on a separate drive, it errors - and from then on, no matter where I try to save, I can't save the file.  If, however, I restart the FSM Editor, and save in the FSM Editor folder (haven't explored other folders on the same drive, yet), I can save as much as I like - just so long as I don't save to another folder on another drive (or I have to restart again).

I think this applies to opening FSM's as well... only seems to work on the same drive.  I imagine there's just an oversight made in passing command-line arguments to the compiler (probably simply missing quotes around pathnames).

Strange behaviour indeed!

[i0n0s]

Have you contacted BIS about this issue?

[JamesF1]

Wouldn't know who to contact about it, to be honest.  I'm pretty sure the CIS isn't the right place for feedback on the tools (or is it?).

[DeanosBeano]

 Sounds very similar to the problems i had with BinPBO when i hadnt cleared my temporary folders on P.
 basicly although i had updated the files ,Binpbo would binarise and pack the old unadjusted ones and there fore no progress was ever made and because the old one was broke and crashed, every subsequent pbo also crashed.

 In essence , maybe when you save your file , you either havent got authorisation to save o er an existing file and your not being warned or because of something very alien that i cant possibly comprehend ,it is saving but not propperly .

 hope that helps.