These are some planned features to the behaviour editor. But they won't be added to the next update.

We're holding off on major changes to the behaviour editor right now. Doing anything with behaviours requires a lot of planning so it doesn't break existing games.

We actually used to support the MFI controllers with joystick controlled, shoot with button, and jump with button behaviours. They would automatically map to the controller.

I don't think the code is removed so they should still work.

The plan was to offer more support for these input devices, but Apple really didn't support the MFI controllers to much. They sort of just released it and left it. So we didn't pursue it either. Maybe once (if/when) we add Apple TV and Mac exporting we'll revisit alternative inputs.

There are ads in the free version of HyperPad. If you've upgraded to indie or developer you should never see ads (even if you cancel developer).

Can you send us a message from the personal support form. This is something @Hamed will look into tomorrow.

@Hamed It would be useful to be able to give the move behaviors priorities, just like with aninations.

If you don't use any of the physics behaviours, and use scenery objects then the physics engine isn't really doing any thing.

So don't use collided, don't use any of the attaches, don't use any forces, etc.

As for drawing lines, we want to add something like this. But need to come up with he best way of doing this.

@This I would agree for adding it to particle inputs for sure! Also being able to change particles dynamically in the game would be sweet!

Post a picture of behaviors. This is most likely a logic issue and not a bug.

@HudsonGami Get the app "Back Eraser" or use something like Pixelmator and make sure you export all your images with transparent backgrounds as PNGs.

Projects in the hub are not Xcode projects but they are native.

If you export you get an Xcode project that you can build as a stand alone (still native) app.

@Murtaza said in Video player:

If you're just using the Play animation behaviour and adding each image individually from the asset library you may notice some performance improvements. What happens is instead of loading each image into memory one by one when needed, it will load the entire sprite sheet at the beginning of the level load.
This increase load times, but decreases any performance hiccups

This is mostly true, but having it not but a single image is better. It takes up less memory when it is setup as a sprite sheet (I forget what we call this in the asset library... i think its an animation?) because there are optimizations in place to use as much space as possible.

@Murtaza Understandable. Thanks.

Hey @Murtaza it's great that you're considering this stuff!

When I mentioned "team names and announcements" I was only adding to the concept of users' Hyperpad websites. Basically, in addition to users' own pages, they can have team pages and send out announcements. They'd have some professional team name - from the App Store, Nitrome would serve the perfect example.

Any other questions?

Hamed:

Now it works and I have remained logged in - despite leaving HyperPad.com.

Thanks.

From the standpoint of any kind of paying user - I think allowing the "Night Time" dark interface theme is quite important.

If you look at the way Unity has restricted a Dark Theme to Pro users - and the resulting uproar among users - it may save you from this kind of flack if you give people a break, now. For many it is a health issue, not a luxury feature or an advanced feature.

I think the tier price points are really reasonable - for nearly every conceivable user - so no change is needed there.

But, the name "Indie" for every platform I can think of implies "making games for money". Perhaps you could consider naming the $4.99 tier to "Enthusiast". I would avoid the name "Hobbyist" like the plague - or even "Amateur". Nobody likes a label that puts them in an inferior category.

This is why, in serious forum circles, the term "Newbie" should be utterly abandoned.

Greg Smith

This is actually something we were planning on doing. As well as being able to reference objects and dynamically put them into Object A / Object B places, or store them into arrays / dictionaries / attributes etc.

However, this is most likely going to be a few updates away.

As stated, the dark theme is part of the developer package.

@TutorialDoctor , I get where you're coming from. But you're not paying for just the dark theme. It's a perk for upgrading, creating a whole package of goodness :).

I have some ideas, where it may let us move the dark theme to the indie tier. But it won't be until we knock out some other updates.

@TutorialDoctor as a workaround, you can set the pause button's colour to be completely transparent and then put a graphic in the UI layer.

Drag and Drop was changed when we switched over to the new physics engine. It's not that great when using with physics since it essentially over rides the physics engine and does its own thing. That's why you can see objects going through other objects sometimes.

For best results, you should probably make your own drag and drop system using the while touching, output the position where you're touching then use move behaviours.