Memory Access violation

About Monkey 2 Forums Monkey 2 Programming Help Memory Access violation

This topic contains 11 replies, has 4 voices, and was last updated by  abakobo 1 year, 3 months ago.

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #12591

    PhatPeter
    Participant

    This is a two part-question.

    The first one is about a memory access violation from missing a New image I’m not sure why I’m getting this error message.

    The second question is about the performance.
    High Sierra sucks big balls and am still waiting for Apple’s bugfixes and the next version of macOS.

    On my main computer I still got Sierra and Monkey1 1.87e as they behave butter smooth and without problems. Love it.
    Of course I needed to be progressive and added Monkey2 but I couldn’t add anything but V1.1.07 to it, as Monkey2 v1.1.08 needs an updated Xcode which in turn needs High sierra and NO I want something that works and am NOT ruining the performance of both of my computers. Updating is scary business !

    The Monkey 1.87e sourcecode works absolutely perfectly smooth (at least on Sierra for now, but probably on higher versions too I just don’t have that many computers to try it on. The important point I wanna make is, It’s 100% stable, never any hiccups, EVER.

    The Monkey2 source code *almost* works, so in any macOS and any M1 and M2 version you use… check those two source codes out and compare them. Notice how M1 is 100% smooth, and how Monkey2 is only 99.9% smooth. I want to know why and if possible… fix it.

    #12592

    PhatPeter
    Participant

    “Included File exceeded size”

    But I want you to see the M1 equvialent code too, so I put it here.

    [/crayon]
    #12593

    PhatPeter
    Participant

    And here’s a sheet.png to use for the examples.

    Attachments:
    #12599

    nerobot
    Participant

    To check memory access violation error you can run your game in debug mode: menu Build — Debug.

    Or you know the line with error but don’t understand why?

    #12600

    PhatPeter
    Participant

    Yes I’m running debug mode, I have no idea why I get the error message though?

    Attachments:
    1. Code.zip
    2. Code-1.zip
    #12603

    PhatPeter
    Participant

    I fixed it, I had missed a asset:: again.

    Now to the main question, there performance of Monkey2. I tried to make the examples as similar to eachoother as I could. Compare the Monkey1 and Monkey2.

    A good way to try these are on a stock new MacBook of some kind.
    The Monkey1 runs perfectly smooth using for example v87e.

    Monkey2 does *almost* run perfectly smooth using one of the last two versions available.

    Why does it not run as smooth? And what to do about it? I’m sure it’s behind the hood so its nothing I could do about it. But why does it happen?

    Attachments:
    1. Debugged.zip
    #12605

    PhatPeter
    Participant

    A stock macbook Air 2015 for instance runs the Monkey1 code 60fps without hiccups for hours.
    Well if you don’t move your mouse and keyboard that is.

    The Monkey2 (You’re forced to use the 1.0.0.7 version bc 1.0.0.8 does not work on stock MacBook wo a xcode/macos update, and you DON’T WANT TO DO THAT YET). Monkey2 works you would think, and it does, but now and then graphical hickups comes around and hit you in the face.

    #12609

    PhatPeter
    Participant

    I guess though it would perform as it should on Android and iOs.

    But, it would be nice if it would perform great once again on macOS too.. I’d love to have a “classic computer platform” that really REALLY works without any flaws.

    Time changes.. this was one year ago, what about now? should I give up on perfect 60 fps with macOS and Monkey2?

    Shoulld I buy an old 2015 MacBook and keep it unupdated forever and just use Monkey1 on it for my “strange retro desires” of having a perfectly smooth computer and language? or will the Monkey2 graphics be fixed for macOS?

    #12613

    Mark Sibly
    Keymaster

    Monkey2 speed on desktop may or may not improve in futre. I am quite happy with the current speed so have no immediate optimization efforts planned. As for the future, I always like to tinker with things so who knows?

    I recommend sticking with monkey1 if you absolutely need the speed you were getting with that and you don’t care about anything else monkey2 has to offer. The cerberus guys seem to be successfully keeping it alive so it wont be going anywhere for a while yet.

    #12615

    PhatPeter
    Participant

    Okay. How about the performances on iOS devices? Do they also differ or do they have a consistent fps quality with M2?

    #12618

    PhatPeter
    Participant

    I wish there could be a “Blitzmode” available, as there were in BlitzBASIC I (as well as II).
    I’m well knowing that platforms such as iOS, Android, Windows, macOS etc would never support such a thing. It’s a pity because sometime realtime and media quality is what you want from your devices.

    #12667

    abakobo
    Participant

    oh man! the generated image is very psychedelic! I had to jump on alt+F4!

    about your code:
    you are using two canvases, canvases slows down you computer, you’d probably will have better perfs with transform matrixes and a single canvas.

    And yes there’s a OnUpdate() event but also OnKeyEvent() and OnMouseEvent(). OnUpdate is not documented though!(will post issue). You can have a look at spacechimps banana to see an example of an app using both OnUpdate() and OnKeyEvent()

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.