PhatPeter

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 83 total)
  • Author
    Posts
  • in reply to: Memory Access violation #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?

    in reply to: Memory Access violation #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.

    in reply to: Memory Access violation #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
    in reply to: Memory Access violation #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
    in reply to: Memory Access violation #12593

    PhatPeter
    Participant

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

    Attachments:
    in reply to: Memory Access violation #12592

    PhatPeter
    Participant

    “Included File exceeded size”

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

    [/crayon]
    in reply to: New empty image #11924

    PhatPeter
    Participant

    Did you solve this?

    in reply to: Mac Icon and its twin #11922

    PhatPeter
    Participant

    I made a temporary solution to save my precocious dock space, I opened up the bin folder and found the icon which apparently was the editor. I copied a png and then opened up info for that file, and pasted the png as the new icon.

    Next time I opened Monkey2 I pinned it onto the dock and threw the original.
    I could’ve Put the original pink icon there as well I just realised. This was just a test.

    One icon – one tool, I’m happy.

    in reply to: Monkey2 conversion #11911

    PhatPeter
    Participant

    For those who are interested it runs perfectly on Lenovo Yoga2 with Android Lollipop. This is too cute, getting 1920×1200 64×64 @ 60 fps. If shaders comes equally cheap on Monkey2 then I will dare to throw MonkeyX away for good.

    I’m curious to see the quality of HTML5 compiling but installing it is a real bitch so I’m giving up on that one for now.

    in reply to: Monkey2 conversion #11910

    PhatPeter
    Participant

    Ops I didn’t notice the post before mine. Thanks I’ll use that instead.

    in reply to: Monkey2 conversion #11909

    PhatPeter
    Participant

    Monkey2 suddenly became a very attractive productivity tool. I’ll get a heart in 3 months.

    But please check into if there is some bug under the hood or not even if this seem to work.
    At least now there’s an easy way to compare the two, just add additional layers and see who drops first.

    in reply to: Monkey2 conversion #11908

    PhatPeter
    Participant

    For anyone who wanna try it !
    still to do is adding input etc, but the skeleton is working in Monkey2. It need a clean up of course.

    I noticed userinputs makes the window or screen a bit wobbly at times so I might check that out what you can do about that.

    Feel free to use this as a banana if you find it useful.

    [/crayon]
    in reply to: Monkey2 conversion #11907

    PhatPeter
    Participant

    Yes I did managed it by myself such victory !!

    in reply to: Monkey2 conversion #11905

    PhatPeter
    Participant

    Your kidding me? haha boy do I feel stupid, 16 hours straight and I miss that.

    Could you list the code because I know not yet how to use “New Int[]”?
    I already include Assets the whole directory?

    in reply to: Monkey2 conversion #11903

    PhatPeter
    Participant

    No direct X. It’s on macOS. I’ve tried windows (OpenGL via angle) and it shows the same amazing performance there. So both are equally good. It’s the same on both platforms.

Viewing 15 posts - 46 through 60 (of 83 total)