User Tag List

Results 1 to 1 of 1

Thread: ZASM Output Error

  1. #1
    The Timelord
    QDB Manager
    ZC Developer

    Join Date
    Oct 2006
    Location
    Prydon Academy
    Posts
    1,396
    Mentioned
    112 Post(s)
    Tagged
    1 Thread(s)
    vBActivity - Stats
    Points
    4,762
    Level
    21
    vBActivity - Bars
    Lv. Percent
    69.24%

    ZASM Output Error

    I'm trying to cross-associate ZScript functions, to ZASM, for the purpose of documentation, and while running qa simple test, compiling and ticking 'Output ZASM to allegro.log', the output was garbage:
    Code:
    Ä
    
    H€Š*y–nit
    
    Ä
    This was produced by placing into the compiler buffer:

    Code:
    global script init{
         void(run){
             Sin(30);
             Rand(40);
         }
    }
    Compile + Output ZASM.

    It seems that the declaration of global script init, on its own, produced corrupted assembly.

    I should be seeing pure ASCII output, with ASM instructions. This looks more like binary code represented as ASCII text... What exactly is happening here?

    Further, despite making a fully new quest, and entering only one global active script into the buffer, then compiling, in the ZASM output, I see these lines:

    Code:
    GhostZHActiveScript
    
    GhostZHActiveScript
    
    Ä
    
    H€Š*y–nit
    How is GhostZHActiveScript being retained, and stored in a log file, for a quest with no active script, and no calls to Ghost.zh at all?

    Is this something Saffith added to ZASM?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Armageddon Games is a game development group founded in 1997. We are extremely passionate about our work and our inspirations are mostly drawn from games of the 8-bit and 16-bit era.
Social