@Perry mm not crashing here, can you check there with the beta release 285.2a
about your post Yves seems give some tips very accurated that you need to follow in the case you want to use among in-App.
Printable View
@Perry mm not crashing here, can you check there with the beta release 285.2a
about your post Yves seems give some tips very accurated that you need to follow in the case you want to use among in-App.
? Where do I find that one?
There is no thread for it.
ooh: I only see an Android 285.2a
Is there also a Fusion 285.2a ??
Could someone from CT please check this: http://bugbox.clickteam.com/issues/3396 and for more info: http://community.clickteam.com/threads/95775-Shaders-looks-different-(bug)-on-two-different-computers
I find this extremely troubling. Any ideas?
no only a android beta to get feedback from user before postQuote:
Originally Posted by Perry
aah ok :)
Might as well remove the IAd from fusion, since Apple is stopping with this one :(
At what point are you guys with these "couple of fixes"? Can you give us some update please?Quote:
Originally Posted by Yves
Well, my best guess is that "a couple of fixes" doesn't necessarily mean "a couple of MINOR fixes", so it's possible that the fixes they want to implement are major fixes... Ya never know. :)
@ J3sseM, I read the report, it is possible that you also add a small mfa recreating the problem, they are a big help to us look the problem.
Any news for the new update?
I have IOS Apps not working for 4 months now , and people complaining about games not working.. :(
-> Perry
What is wrong with your app ? Is it a problem with iOS exporter ?
@ MagnetoX Yes IOS Exporter.. Some issues are fixed from what I know.. and more related to the Ipad pro. and hopefully also Xcode 7.
But my Ipad pro users are complaining about buttons and images shifted... (and that was fixed)
SubApp issue with Ipad Pro as well. (not sure if that was fixed)
Almost six months are passed from the latest beta update, do you have some news?
I think they have been busy preparing Fusion 3 for upcoming GDC... and Fernando is the only dev that I've seen pretty active developing Android build.
This situation already has 1 year and a little more in iOS.
Sorry we are all active here, only that some of us are focus in a specific products or new product (don't you guys?, are you anxious with F3?, I am), so be sure we are all working to give you a better products each day.
I think the frustration is coming in place with the statement in November from Yves wrapping up a few bugs.
Then IOS is failing for Ipad Pro, Xcode 7.x (more settings and changes) and some items not working.
Now they are working on IOS 9.3 Beta and IOS 10.x Beta... So time goes fast.
Then Google throws out there message about their security, so now things piling up, and no update is coming.
I agree Perry!😡
Is iOS currently a mess? I want to start converting a Windows program to iPad, which isn't gonna be a quick process, but in terrified it won't be stable due to all the iOS shifting and Clickteam having to keep up with it all. Apple makes things tricky!
It is not a disaster, nor to do so, it is more I dare say that it is one of the best exporters because they go directly to Xcode.
What happens is that she has not been updated for quite some time and has problems with Xcode 7 and some reported bugs that have not been resolved.
Anders has always been the leader of the project but now is too busy with F3 and need to spend you time to resolve issues at F2.5
I released an iOS app a few years ago and I remember it being quite a pain getting up to speed with Xcode and all that Apple required...then they changed the playing field without notice! It's that sort of upkeep I'm not looking forward to, especially with Clickteam being a necessary middleman. Not that I have any blame for them. It's not easy for me to keep up with Apple and I know Clickteam is just trying to do the same.
Exactly dude, in this Clickteam must be very a day by the number of changes generated by Apple and is that it's work, but now it is collecting and they as a company must give support so that we can have our apps a day and we can upload them without problems to the App Store. In this moment is almost impossible to climb a game with Xcode 7, the friend Perry has some solutions but is a process tedious.
I wouldn't say the exporter is a mess at all. But you also need to limit your expectations a bit and not expect support of Apple's newest bells and whistles. If your game is aiming to use pre-iOS7 features and technology, you will be fine. If you want to use Apple specific features from the iOS7 era and beyond, then you will need to manually modify your project in Xcode. One of the biggest headaches with Xcode these days is that while a lot of things are automated, sometimes they don't work. So simply restarting your Mac or Xcode will often fix failed builds. Also, each new Xcode often reorganizes the UI so finding where things are is often a headache if you haven't been in Xcode for a while. I can sympathize with Clickteam's situation entirely. They have a limited staff to work on this stuff and F3 is a big priority, I'm sure. Honestly, if F3 ships this year and has a more robust iOS exporter at launch, then all this waiting will be worth it. Fingers crossed... :)
@Mobichan. Apple doesn't allow you to update with an older version. if you are on OS 10.11 you are STUCK with Xcode 7.x.x
Besides that, Xcode 6, doesn't support all the newer Ipads, so you will get complaints from those customers.
So is updating Xcode not recommended?Quote:
Originally Posted by Perry
If you are on OS 10.10 and Xcode 6, then you are OK (if you updated your device to IOS 9.x then you cannot Test anymore and requires Xcode 7, and Xcode 7 does not work on OS 10.10)
if you are on OS 10.11 then your out of luck. (Xcode 7 does work, but you need to make changes to the plist in order to submit your apps)
But newer devices won't work properly
Good summary Perry. BTW fully I understand the point of Mobichan and I also want a good F3 with a robust exporter. I do not ask for new features at this point but to work properly on iOS 9 and Xcode 7.
I was not at all saying you shouldn't update your xcode version. You should. And if you need to support older OS versions than the current Xcode allows, you need to keep a test device with that OS version for test (which kind of sucks). This fact is a terrible truth of working in the Apple ecosystem, which promotes people to buy the newest thing and throw away old tech at a frequent pace. I was only trying to say that using the MMF exporter is fine if you are using the latest Xcode version to compile. And as long as you are making apps with features that existed before iOS7, you will be fine.
If you are trying to live on the bleeding edge of Apple innovation and are playing with Betas, then you should consider not using MMF or accept the fact that you will probably run into bugs that won't be fixed immediately.
thanks for your update
Mobichan sorry if my English is bad and I do not understand (my native language is Spanish), what I mean is that we have more than 8 months without an update of iOS exporter, and now you can not upload an app developed in F2.5 from Xcode 7 (not beta) to the AppStore, you can not upload more compile also missing topics as unsupported icons, editions in Xcode to work things like those reported by Perry, etc ... Shoving all this, Clickteam only supported Android exporter accurately by Fernando but can not be almost a year to support the exporter which I dare say is the one that generates more money to us as developers.Quote:
Originally Posted by mobichan
The last time was to fix something at iOS exporter was on January 14, 2014 as the log file of the beta 285.1.
There is no review for a year and two months. Incredible! >:D
Ugh...really? That's pretty rough.Quote:
Originally Posted by Koji_Kabuto
Since months I ask myself if it is wise to invest more money in the future into a company with this extremely customer-unfriendly update philosophy and customer communication philosophy...Quote:
only supported Android exporter accurately by Fernando but can not be almost a year to support the exporter
I doubt that their internal problems will magically disappear in the future. An actual problem seems that the programmers are completely overstrained with developing 3 and fixing 2.5 (especially the iOS exporter).
Keep in mind that with any product, there usually are bugs to work out... overall, I believe the IOS exporter is a very stable platform. Even with the bugs I've experienced, I'm still quite happy with the product. Fusion 3 is a total re-write, which is a major task. I believe we'll see Clickteam members become more responsive in the VERY near future. I know I had my own complaints, but the big picture shows a bright future for all of us.
Why wouldn't clickteam just update all this stuff to the latest compatibility fix... even without the additional features...
Just fix the bugs, the issues, and some minor stuff Right Away... I would be so happy... we all would...
Just please don't let clickteam be left behind by other engines... Just make your customers happy, these are the same people who would likely Buy Fusion 3.
It's really hard to trust Fusion 3 if 2.5 was left behind too much, coz it gives the impression of Fusion 3 being left behind also after a year or two, or just painfully slow engine development, either way it's sad.
I like Fusion, I've used it ever since, It's my first love, I earn with it, it's somehow great; but if my freaking game breaks and crashes, and I cannot easily export, also waited for ages for an update fix...
I might need to move on... I don't want to move on :( Don't die on me
Exactly...Quote:
It's really hard to trust Fusion 3 if 2.5 was left behind too much
I agree also...
Gents, in order to help F3 development I will start to help anders in iOS, but please give me some time to get wet in this.
wpd & tom79: I find it hard to swallow what you are saying here. Fusion 2.5 is basically a feature upgrade from MMF2. This makes it a product that has been around for at least 8 years (when I began using MMF2). To say F3 would not have a decent lifespan doesn't make sense. And to say F2.5 should be supported longer, well, can you name another creative tool that has lasted that long with support from it's parent company? From what Jeff told me, there are plans to support Clickteam products for 5 or more years whenever a license deal is signed with any educational institution. But this means that the products will be serviced and repaired when faced with OS incompatibility or something similarly catastrophic. Asking any company to simply keep polishing and adding features to a very old product is just silly. Regardless of what you might want, this is the nature of ALL software, excluding open source or collaborative online software development (which F2.5 is not).
I think you need to accept the reality that you are using a very mature product that has a long history of evolving and improving. But those "improvements" MUST end in order for Clickteam to make their next product the best it can be. We are at the transition period now, so work on F2.5 is going to trickle off. If a Kickstarter can be worked out, maybe there will be one last big feature push, but with limited resources, Clickteam can only do so much without additional staff.
Absolutely correct. It must end but I think the community need a working version 2.5 while waiting years for a working version 3. When was the last iOS exporter update?... There are people here who make a living using such software who can not wait years of interruption.Quote:
But those "improvements" MUST end in order for Clickteam to make their next product
Also you have to see the lifespan of 2.5 and the exporters separated from the lifespan of 2.0 and older.
If a company advertises a new upgraded software version with more features and addons they should update it regularly but the above-average bugs from the beginning of 2.5 (especially in the exporters) combined with the irregular and slow updates compared to the competition (besides the android exporter thanks to Fernando) and the unannounced stop of updates for the iOS exporter for this long time period does not create trust regarding competence in team and time management as well as communication skills.
That's also my opinion. Adding features is silly. I wrote it in another thread. But fixing bugs regularly for an adequate time is an essential condition.Quote:
adding features to a very old product is just silly
That's also correct but clickteam could have additional staff. The kickstarter idea shows that people would pay them more money to get things done (and fixed) more quickly. Now see above... "competence in team and time management as well as communication skills" The market does not wait for us developers.Quote:
Clickteam can only do so much without additional staff.
@Fernando Good news!Quote:
I will start to help anders in iOS, but please give me some time to get wet in this.
Fernando YOUR THE MAN!!! :DQuote:
Originally Posted by Fernando
Dive in & soak it up!