KrystalOS 2 (Suggestions)
-
@iTap-Development Okay, thank you. Just let me know when you’re done, I will definitely credit you.
@Kamdroid I've found at least one (possibly two) of the major sources of the slowdowns and weird bugs in hyperPad, and its memory leakage, which causes much worse shit eventually...
This is the same reason your little jump game, once it starts stuttering, continues to do so.
It's the same pair of reasons that the editor heats up your iPad and flattens its battery, hard.. to... and it's getting worse for me now because I'm starting to use more content and make much heavier demands of the editor and game running. So I did a bit of poking around with the profiler and watched this app leak memory.
It takes a long time using the app, though, consistently, to see this one get really bad on the 4GB of an iPad Pro, but eventually this what caused the nightmare with the arrays I had that got everyone out of shape. I knew, at the time, that this was a systemic indicator of a much bigger bug, one that I am quite sure @hamed MUST know about, since he's surely profiled his own app and found the problem, been unable to fix it, and used a "crash on reboot" to cause a flushing of that memory to initiate for a while... before it goes nuts again.
When you have a project with a lot of big graphics, you get to see and feel this earlier and harder than others. Which is why I have noticed it more than most others, I'm using a lot of big textures.
-
@Kamdroid I've found at least one (possibly two) of the major sources of the slowdowns and weird bugs in hyperPad, and its memory leakage, which causes much worse shit eventually...
This is the same reason your little jump game, once it starts stuttering, continues to do so.
It's the same pair of reasons that the editor heats up your iPad and flattens its battery, hard.. to... and it's getting worse for me now because I'm starting to use more content and make much heavier demands of the editor and game running. So I did a bit of poking around with the profiler and watched this app leak memory.
It takes a long time using the app, though, consistently, to see this one get really bad on the 4GB of an iPad Pro, but eventually this what caused the nightmare with the arrays I had that got everyone out of shape. I knew, at the time, that this was a systemic indicator of a much bigger bug, one that I am quite sure @hamed MUST know about, since he's surely profiled his own app and found the problem, been unable to fix it, and used a "crash on reboot" to cause a flushing of that memory to initiate for a while... before it goes nuts again.
When you have a project with a lot of big graphics, you get to see and feel this earlier and harder than others. Which is why I have noticed it more than most others, I'm using a lot of big textures.
@Deeeds I reckon it might be a bug with this new release of HyperPad, or something with iOS 11, but I can’t say for sure, since no one else said anything about stutter yet.
The game is very simple and isn’t doing any complex stuff, it just spawns stuff every few seconds and that moves to the left until it’s off screen then destroys itself
-
Got the folder system finished, wow, thought I wouldn’t be able to.
Some stuff still needs to be cleaned up but it’s all working.Drag and drop an app on a folder to put it in the folder, tap the folder to open it, and you can also still move around folders etc as it still derived from the app core object.
-
Got the folder system finished, wow, thought I wouldn’t be able to.
Some stuff still needs to be cleaned up but it’s all working.Drag and drop an app on a folder to put it in the folder, tap the folder to open it, and you can also still move around folders etc as it still derived from the app core object.
@Kamdroid WOW.
The manner in which you know the capabilities and methodologies of hyperPad must be quite thorough for you to conceive of and then build something like this. It's incredible.
I am abusing a "low code" policy and physics to do just about everything, and adapt my game design to the limitations I find in hyperPad, mostly.
So to see something like this, a huge initiative with determination, it's incredible.
WELL DONE!
btw, I've been meaning to say this: Well done on all the little animations and use of transitions and fades to foretell and ease in and out the movements. Great consideration of the user experience and guidance of their focus. It was very noticeable on the little jump game where you had a first title screen that was basic, but clean and enjoyably animated, and every little movement in this Krystal OS. VERY GOOD!
-
Got the folder system finished, wow, thought I wouldn’t be able to.
Some stuff still needs to be cleaned up but it’s all working.Drag and drop an app on a folder to put it in the folder, tap the folder to open it, and you can also still move around folders etc as it still derived from the app core object.
@Kamdroid I've just requested an Xcode project for a demo scene I made, so I could look at the cocos2D code.
It is as I suspected. They rely way to heavily on CADisplayLink, which is an unreliable mechanism, and upon which the reliance causes known bugs in cocos2D. One of those is memory leakage, another is the dropped frames (the stuttering) and a third is a generally diminishing responsiveness and performance that's only possible to 'fix' by closing the app or initiating an iOS system call that "backgrounds" the app. That's an up-swipe, down-swipe, app-switch swipe, pinch with four/five fingers or double tap the home button.
Do you have a Dev Account and Xcode? I can show you how to manually fix this and gain significant improvements in the consistency of performance in your games, and stop memory leaks.
-
@Kamdroid I've just requested an Xcode project for a demo scene I made, so I could look at the cocos2D code.
It is as I suspected. They rely way to heavily on CADisplayLink, which is an unreliable mechanism, and upon which the reliance causes known bugs in cocos2D. One of those is memory leakage, another is the dropped frames (the stuttering) and a third is a generally diminishing responsiveness and performance that's only possible to 'fix' by closing the app or initiating an iOS system call that "backgrounds" the app. That's an up-swipe, down-swipe, app-switch swipe, pinch with four/five fingers or double tap the home button.
Do you have a Dev Account and Xcode? I can show you how to manually fix this and gain significant improvements in the consistency of performance in your games, and stop memory leaks.
-
@Deeeds I don’t have one yet. I’d probably only get one when I’m full blown creating apps/games for the App Store.
-
@Kamdroid Ok.
Are you at all familiar with Objective-C, Swift and/or any Apple Frameworks/SDKs?
-
@Deeeds I know, but I don't like Java. And Xamarin is pretty good, and it also supports cross platform apps
@Kamdroid I think Xamarin is one of the most impressive software endeavours I've seen in a long while. The incorporation of frameworks, natively, is incredible.
The odd thing, this (worthy) project nearly starved to death not so long ago. Now it's THRIVING.
-
I've kind of stopped development on this, because I have other projects.
When iTapDevelopment finishes his scroll system, I'll create some basic "apps", so it's not as empty, and release it to the hub.Although this is an improvement from the previous KrystalOS, I think I should wait until object referencing for loops (being able to manipulate a spawned object, e.g. set attribute, set color etc).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login