Executable not being created

Posted By: Ruben

Executable not being created - 09/01/17 10:19

I am trying to create an executable (.EXE Application file) for my game. I took out what I thought to be all the errors that showed up when compiling the executable. I am not getting any more errors, and it compiles all the way, and it creates the .cd folder, but I am not finding the .EXE Application file to run the game. I thought I had the right Gamestudio version needed to create a game executable. It has been quite a while since I tried to create an executable. Does that service expire after a certain period of time? Is there something I may be doing wrong in creating the executable?

Posted By: Kartoffel

Re: Executable not being created - 09/01/17 11:08

make sure that 'compile exe' is checked (should be checked by default) and take a look at your antivirus software (it might move the executable straigt to quarantine or even remove it completely)

Posted By: Ruben

Re: Executable not being created - 09/02/17 02:16

Thank you Kartoffel. I looked in my quarantined items in Microsoft Security Essentials, and do not see anything resembling a .EXE file from Gamestudio.

If the .EXE Application file is created after compiling, doesn't it say so at the end of the compilation? I do not think I see anything in the small compile window stating that a .EXE Application file was made, even though I see no errors being given.

Posted By: Ruben

Re: Executable not being created - 09/02/17 02:38

This is what shows up in my compiler after it goes through all the numbered file names:

Code:

...

MAP Entities:
1.  crystal_large.mdl
Autobind:
1.  C:UsersRubenDesktopGamestudio Backup FilesDEMO GAMEDemo Game FilesGamestudio Backup Files - NEWGamestudio A7 Working Filesacknex.wdf
2.  C:Program FilesGStudio8d3dx9_42.dll

subdirectory created:
c:usersrubendesktopgamestudio backup filesdemo gamedemo game filesgamestudio backup files - newgamestudio a7 working filesdemo.cd

(Keep in mind that the filenames are separated by the backward slash symbol, but this forum is not saving that symbol for some reason.)

It used to say that the acknex.wdf was being skipped. I saw that it was not saved in the "Autobind: 1." location, so I took an acknex.wdf file from somewhere else, and pasted into the location to stop giving the "Skipped" error. Not sure if that is why the .EXE Application file is not being created.

Posted By: alibaba

Re: Executable not being created - 09/02/17 03:12

I'm pretty sure it has something to do with the length of the path. Try publishing it somewhere else, like in the root of the C:/ drive, just for testing purposes.

Posted By: Ruben

Re: Executable not being created - 09/02/17 05:17

Thank you alibaba. Sorry for my ignorance, but I was not aware that one could alter the location on where the .EXE Application file gets saved. I thought it only gets saved in the same folder as the main script.

I tried looking in the manual and online, but cannot find out how to specify where to save the .EXE Application file other than the same file as the main script. Any clue on how to do it?