Posts by J3sseM

Not sure if this has been found previously, but with my new game I'm working on, I noticed that:

A) It's butter smooth when in windowed mode and NOT maximized.
B) If I maximize the screen (not real fullscreen but windowed fullscreen) I get nasty micro-stutter quite constantly.

I tried resizing the game-window to about 95% of my screen size (4k monitor and resolution if that matters) and it's still butter smooth. If I maximize the window, BOOOM stutter.

Not sure what that means? I think I'll do some more experimenting tomorrow.

I bought it but couldn't get it to work at all. I used Android Object's built-in function to build support for a gamepad.
Still not sure what this object even does. O_o

Quote from danjo

and you got what to lose?

A lot, betas are bound to have more issues. Besides, my errors seem to be different and not related to IAP.

Quote from Perry

This is fixed in the latest Beta.

Huh, you sure? :O

Quote from Perry

Did you update to the new Beta?

No. I'm only using the release versions. But this seems worrying!

Lots of crashes here too, with latest version on Steam:

Build API: 25, OpenGL ES 2.0

java.lang.RuntimeException: 
  at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2638)
  at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2720)
  at android.app.ActivityThread.access$900 (ActivityThread.java:196)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1538)
  at android.os.Handler.dispatchMessage (Handler.java:111)
  at android.os.Looper.loop (Looper.java:210)
  at android.app.ActivityThread.main (ActivityThread.java:5982)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:852)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:742)
Caused by: java.lang.NullPointerException: 
  at Runtime.MMFRuntime.onStart (MMFRuntime.java)
  at android.app.Instrumentation.callActivityOnStart (Instrumentation.java:1249)
  at android.app.Activity.performStart (Activity.java:6464)
  at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2595)

Paid game, and I can see lots of refunds - related to this?

I remember having this very problem. In the end, I couldn't find a solution, so I took Joystick 2 out of my game and went with Xbox Controller object only.

Thanks for the reply wpd!

I did submit to bug-tracker. This shouldn't be a problem when using "final build". Anyway, I went ahead and deleted all IronSource related files and that worked as well.

Thanks though!

Jesse

Hey guys,

I'm posting here because iOS thread doesn't get that much traffic.
Now, I bought IronSource object some time ago, I installed it, and after that, I can't build anything with Xcode. It always gives me an error: 'IronSource/IronSource.h' file not found, and the build fails.
It's possible I'm simply missing something, but it refers to that very object I'm not even using. In fact, I can't even build an empty application anymore.

Quick help would be appreciated.

Thanks,

Jesse

Yes, Windows 10, but surely there must be a way to avoid blurry text on HTML5.

Yes, String object, and I've tried both with AA and without AA. Mmm, I bet I'm missing something as I can't find any other threads about the same problem.

Quote from danworth

I'll have to check my self. but if I remember correctly when built in HTML5 you can alter the compiled application settings by editing the package files manually.

I tried altering the index.html file style, but that had no effect.
Maybe we need to alter runtime.js file it generates? :O

I'd really appreciate help with this, so if you've time to check it out that'd be great.

Quote from danworth

Maybe altering the text-rendering css attribute on the compiled app pages can help?

Huh interesting idea, not sure altering that would alter the text in-game, though? I'll see if I can figure out how to give it a try.
Thanks btw!

Jesse

Not 100% the same, for example in Firefox it's slightly crisper than in Chrome, but still blurred.

Hello,

Not sure if I'm going to get a reply here, seems super quiet!
Anyway, I'm looking to achieve a crisp dialogue. Everything works just fine in Fusion 2.5, but when I build and run, I get the blurry font. (please, click to view bigger)
Please login to see this attachment.

I've tried both AA and without AA. Hopefully, there's just something simple I'm missing.

Any help would be appreciated.

Thanks!

Jesse

Ah just noticed, from Bug Tracker:
"Fixed in build 291."

Excellent!

I might have the same problem. I didn't try to solve it yet, though, as I'm doing some other stuff for now.
But with a quick test, that very thing happened to me as well. Did you manage to solve this?

I'll let you know if I find a way around!

Totally missed this, whoa! :O

The answer is "perhaps", but most likely "no".
Would be awesome, I expect to start porting DISTRAINT 2 to mobile devices around next summer. If we had shader support, it would be so, so much easier.

Anyway, I wouldn't count on it. We need to find alternative ways and make compromises, though in today's competitive market it most definitely doesn't help.

Fingers crossed Fusion 3.0 is coming soon and has all that functionality!

I gotta say, I'm super confused about this. I think there are too many things going on at once.
I think we need super simple .mfa that will stutter for some people and not for some. Then, we could measure the stuttering using the FRAPS tool for example (just to see if our outputs differs)!
At first, we need to check the example without FRAPS running in the background as we don't know if that can cause stuttering as well.

After that, we should measure using FRAPS and post the results here. We should be seeing very different kind of outputs that way. It would clear things up!

By the way, I'm getting some micro-stuttering from using deltatime, I will need to take a closer look, though, as it can be a problem with scrolling rather than stuttering. You know, value going from 0,xxx to 1,xxx -> and jumping that pixel, appearing to stutter.

However, at the moment we have too many "yes", "no", "ifs" and "buts".