GM:S 1.4 How useful is GM:S 1.4 ?

Discussion in 'Legacy GameMaker Community Tech Support' started by NeZvers, Jul 9, 2019.

  1. NeZvers

    NeZvers Member

    Joined:
    Mar 24, 2018
    Posts:
    318
    I have licenses for desktops, html5, Android, iOS. Can I still publish to them?
    I've upgraded to GM:S 2 but that doesn't carry over licenses and got me down. I now feel more confident about developing and have solid ideas for real publishable games and that's where I start to worry about 1.4 exports.

    I know Windows and html5 are still working.
     
  2. TsukaYuriko

    TsukaYuriko Q&A Spawn Camper Forum Staff Moderator

    Joined:
    Apr 21, 2016
    Posts:
    1,470
    These exports will continue to work properly until a third party that is involved with the process changes something that invalidates the way the export modules work, such as the impending changes to Google Play that will disallow 32-bit apps and therefore break the 1.4 Android export. So, for now, they might still work, but I wouldn't count on it, as once the bomb drops, nothing can be done to prevent it from going off. GMS 2 is the way to go forward.
     
    EvanSki likes this.
  3. curato

    curato Member

    Joined:
    Jun 30, 2016
    Posts:
    219
    Worst case, if you have to convert to GMS2, I haven't seen any real issue with converting my projects. They all seem to work right away.
     
  4. NeZvers

    NeZvers Member

    Joined:
    Mar 24, 2018
    Posts:
    318
    I have no problem with converting to GM:S2 or working in it. I actually love workflow in GM:S2.
     
  5. 00.Archer

    00.Archer Member

    Joined:
    Jul 24, 2018
    Posts:
    55
    I'd add that the desktop export will probably keep working fine for a long time.
     
    Lonewolff likes this.
  6. Lonewolff

    Lonewolff Member

    Joined:
    Jan 8, 2018
    Posts:
    1,084
    Agreed.

    Windows export will work forever, unless MS does something extremely stupid that breaks most games out there (GM made or not).
     
  7. EvanSki

    EvanSki King of Raccoons

    Joined:
    Apr 17, 2018
    Posts:
    492
    Lots of companies, operating systems, and software are phasing out X32 bit support, soo better use it before 2023
     
  8. EvanSki

    EvanSki King of Raccoons

    Joined:
    Apr 17, 2018
    Posts:
    492
    At the most before the year 2038, um (ask your parents about the Y2K) (depending on your age) event then check out Y2K38

    [​IMG]
     
    00.Archer likes this.
  9. Lonewolff

    Lonewolff Member

    Joined:
    Jan 8, 2018
    Posts:
    1,084
    Yes, this is true.

    But, I can't see Microsoft suddenly saying 'we are now blocking 32 bit programs for Windows 7 through to Windows 10'.

    Apple though, they are a different breed. Wouldn't surprise me with anything they do.


    My parents didn't have a clue about the Y2K bug. They were 60 when that was a thing.
     
    EvanSki likes this.
  10. EvanSki

    EvanSki King of Raccoons

    Joined:
    Apr 17, 2018
    Posts:
    492
    Windows 1X or whatever stupid name they call it did we even get windows 9?

    EDIT:so microsoft isnt going to make a new windows version rather they will just keep updating windows 10 sooo Windows10x


    I was born after it so I didnt know it was a thing until last year and im a huge computer nerd, never crossed my mind about the storage of time, figured it would all be emulated from a server that actually runs and stores the time like time.gov (meaning your computer would connect to time.gov to get the time, and the data center for time.gov would actually hold the memory and just be updated, but you see how they do updates)
     
    Last edited: Jul 11, 2019 at 2:27 AM
  11. Lonewolff

    Lonewolff Member

    Joined:
    Jan 8, 2018
    Posts:
    1,084
    There is historical reasons why they couldn't call it Windows 9.

    Mainly due to windows version information. Older applications would check to see if the windows version was 9x (Windows 95 and 98). So you can see pretty quickly where things might go amiss when a pre-WinNT application queries the registry to see that it is running on Windows 9. It would see that it is running on the 'correct' operating system.



    A lot of it was a BIOS thing. BIOS'es don't generally have the ability to see time servers. Not that it would make a difference, because the offending BIOS'es didn't store the century they we living in.

    Even if the BIOS did talk to the time server, the BIOS would go and store 2019 as 1919. The other half of the millenium bug was poorly written applications that only stored the two least significant digits of the year, running into the same problem.
     
    EvanSki likes this.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice