I'd recommend everyone who's currently wearing headphones not to hover over this video.
I'd recommend everyone who's currently wearing headphones not to hover over this video.
they're on their own now, we're on page 48
Phyzicle Android device test: http://puu.sh/r73Y
This is a stripped down version of Phyzicle only meant to test device compability! There's no saving/loading/community functionality, and a few other things have been taken out. The final release is coming soon, though!
NOTE: Don't send me any feedback via the built-in forms yet, they don't do anything for now.
Please reply with:
1) Device information (manufacturer, model, hardware, etc.)
2) OS information (Android version, any custom ROMs, etc.)
3) Result of running Phyzicle (any issues? or does it run well?)
Please be specific!
Please do NOT reply with:
- "hurr durr it doesn't work!"
- "hurr why can't I download levels?!?"
etc.
Thanks!
Also, feel free to like the Facebook page :) http://www.facebook.com/Phyzicle - it'll have information on the public release!
Good thing that I'm so turned off by garry's HTML5 coolness that I completely disabled <video> tags on FP.
-snip-
I just disabled Media Autoplay in the about:config page in Firefox.
Working on a space background generator. After I've added support for sprite layers, I'm going to make an exporter to parallax scrolling.
1) HTC Wildfire (Shitty I know)
2) CyanogenMod 9
3) Runs well although the UI is a bit small
Oh shit, I forgot that Facepunch can't tolerate anything Japanese. Sorry about that.
The original Wildfire? The one that runs at 320x240?
Edited:
If yes, then I'm not surprised the UI feels a bit smallQuite frankly, optimizing the UI for such a small resolution would be a difficult task. I'm more surprised that it runs at all :D
Besides the aforementioned fact that if one accidentally scrolls over a video it rapes your ears and scares the shit out of you, it wastes a sizeable amount of my 1Mbps connection and too many of them on one page (read: highlights) slows my CPU to a crawl in Chrome.
Edited:
Oh, and I know it may come as a shock to garry, but I prefer to watch videos from the beginning and I'm incapable of watching multiple videos at the same time so there's really no reason to autoplay everything.
So what you moaning for then?
I like videos autoplaying. I don't get any issues with sound. I like it the way it is, you like it the way you have it set up. No need to change anything :)
Bandwidth would be an issue whatever I did with HTML5 videos - I'm not going to go out of my way to trick it into not preloading.
1) HTC Sensation
2) Android ICS 4.0.3
3) I often find myself clicking a UI button multiple times before it does what it's supposed to do.
It will flash as if I've clicked it but nothing would happen.
I also keep moving things when I try to move the camera. This is because if you place your finger on an object and move your finger, the object moves. But if your screen is filled with objects it's rather hard to move the camera around since there's barely any place to put your finger without moving things.
Other than that there hasn't been a single problem so far.
As an aside note, how do I freeze an object?
Edited:
UI doesn't feel small here
It's quite pleasant to use to be honest.
Thanks.
Tap the screen 5 times (tap tap tap tap tap quickly) until the console comes up. Type in "touchpx 15" - this controls the pixel radius for touches. Some devices are *far* more sensitive than others and need a much more lenient touch radius. Let me know if that fixes the issue (also try "touchpx 20", etc.)
Tap the little camera button on the top left. It'll enable camera-mode so you can move the camera instead of the objects.
Select it, side menu, "Static"
Trying to be helpful. I think you need to do some work in making those bottom two features more obvious.
Can you give us one good reason why autoplaying is useful and not just a shiny HTML5 feature you couldn't resist shitting all over the forum?
I'm not sure how; any ideas? They're already in the documentation/tutorials. I'll add a FAQ, maybe that'll help.
I think the problem is that whilst I'm touching the button, my finger moves slightly. When I'm using the toolbar at the bottom every once in a while it moves even though I'm clicking, not dragging.
This works, but could you make it so if you press the camera button you'd stop using the tools? I had the rectangle tool selected, pressed the camera button and tried to move my camera but then I created a rectangle
Thank you, I froze it by using 8 rods to keep it in place
Edited:
By the way, try notifying the user of the manual the first time the game is played. I hadn't noticed it until you mentioned it.
Yes that's the problem; like I said, some devices are far more sensitive than others and require a much different radius for a touch to be consider a tap. Did you try "touchpx 15" or "touchpx 20" like I suggested?
Good idea.
You don't have to click anything. Do you want a play button on animated GIF's too?
That's not a bad idea actually (the GIF play button).
Edit: In general though, videos are usually longer than GIFs so you'd want to make sure you're starting at the beginning.
Then start using Opera, I believe they have a few features you'd like.
I had tried 15 and 20, in the end 25 did the trick.
Thanks for the info. This is an intriguing problem, I wonder how other apps handle it. Some devices just have insanely sensitive screens (your device), others have much less sensitivity (iPhone4S, for example).
GIFs don't have sound.
Samsung galaxy 3/apollo
Kyrillos mod v9.5
Doesnt start, I launch it, a black screen shows up and ten 5 seconds after it goes back to the homescreen
I don't want to be a dick but it's Garry's forums. He decides what to do with it, if you don't like it get out.
That's odd. Do you know how to get the log, by any chance?
If you know how to use adb, do:
To clear the log, then launch the app, wait for it to close, and do:Code:adb logcat -c
Then post/send me that if you can :)Code:adb logcat -d > log.txt
Could you make the gridsize adjustable by a slider, instead of just by zooming? It's rather annoying to place a motor at the center of a gear if the grid isn't aligned with the gear. Having to zoom in and forgetting that you need to click the camera button in order to not move stuff around just ruined my contraption :|
Tap undo.
Edited:
Also use the "Snap to Center" feature for gears, far easier.
1) Samsung Galaxy S+ (GT-I9001)
2) 2.3.5 default rom
3) Performance is very good.
I think you should add support for Android's hardware buttons (back button and menu button). I did not find any way to shut down the app without pressing home button and then shutting it down from task manager, so an exit button would be appreciated.
1) Amazon Kindle Fire
2) ICS V4.0.4 (CyanogenMod9)
3) Installed fine, runs flawlessly, but as stated before there are some issues with pressing buttons, mainly on the toolbar. Either I press the button, see it "depress" and let up only to find I had either moved my finger or had not pressed down hard enough/long enough for it to register. This got pretty annoying pretty quickly, but besides this everything (including the icon) looks and works great.
If you're using the webm tags for actual video, you're doing it wrong. The webm tag was supposed to be a replacement for the bulky and colour-lacking gif animations posted in here.
If you want to post a video where you're showcasing a bunch of stuff, upload an unlisted video to YouTube.
It would be just fine if videos autoplayed but didn't have the sound.
You get a better alternative to a gif without the danger of someone being too lazy to strip the audio and edit the post.
You're insanely zoomed out, you can tell by the size of the fluid particles. There's a limit to the amount of fluid (4096 particles) and it might lag.
Yup, I'm going to look into adding support for the hardware buttons.
As for exiting: this has been a long, long discussion on sites like stackoverflow. The general conclusion is that Android apps should not exit on their own, it goes against Android's philosophy; the OS itself will close an app if it deems it necessary.
Thanks for the info. Tap 5 times (tap tap tap tap tap quickly), type in "touchpx 20" and tell me if the problem goes away. Some devices are far more sensitive than others when it comes to taps vs. dragging.
GIF != WebM
Also, WebM is used a lot more often on this forum than GIFs.
Edited:
Also, I'd rather have click-to-play than insta-earrape when scrolling the thread with my mouse on the left side.
Made this:
Yup, that's pretty much it...
1) Samsung Nexus S
2) Stock 4.0.3
3) :
Runs pretty well. It starts slowing down the more things you have on screen as you'd expect, but it seems slower than some other physics games I've played.
The pause/play button was pretty fiddly, might want to make that larger so it's easier to press. Also, why is there a huge rectangle on the right hand side for the menu when android phones have a menu button?