adrix89's Forum Posts

  • Aeal5566

    I can download just fine

    Heres a link if you have problems

    http://dl.dropbox.com/u/1027218/Spricer.zip

    madster

    The purpose of the program is to take a big image and transform into lots of smaller images and has to check every pixel for it to do this

    Its not that strange if you ask me

    After all its not powered by magic so as to magically know where to cut

    Also note that the alternative is that you have to do it by hand every 1 even if it has 10000 frames

  • It doesn't "fix" physics...

    ...

    Also, hinges work.

    Stop it right there! I need hinges to work why isn't this fix committed to the project?

    Also can someone make a compiled exe seeming as we run different versions?

  • I found out that when hinged box2d simulates the hinged object with a 90* offset

    Most likely the box2d b2RevoluteJoint.cpp

    referenceAngle = bodyB->GetAngle() - bodyA->GetAngle();

    line causes it

    Which means that box2d angles and construct angles aren't synchronized

    http://dl.dropbox.com/u/1027218/bug3.cap

    Also Stiffness seems to be deprecated as its not used anywhere

  • There is also http://animata.kibu.hu/

    However they don't have any export to png so you would have to play with the video stream if you wan't to so something with it

    [quote:1xjrntun]PAP - Plastic Animation Paper

    Specialized on animation (no coloring or compositing) and completely free since July 23

    Oh god! that interface!

  • I think i solved it , well kind of.Ive changed the linear damping to 100% for all three.Here's the reworked cap.

    http://dl.dropbox.com/u/7658043/workingsortoff.cap

    linear and angle dampening acts like a sort of friction for movement and rotation

    You cannot really fix something that is essentially a bug report without going through the C++ code

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Hmm I see ellipse crashes when hinged

  • I'm using the latest version(0.99.92) and the physics seem to be really bugged

    First setting sprites to collision ellipse crashes the program

    Second the hinge seems to interpret gravity(or some other force) on the left rather then bottom

    Third in some strange situation it doesn't even hinge for some reason

    Forth when hinged in some situations the physics collide at an offset

    Can someone confirm some of this bugs?

    Also if it seems to work for you can you try to make an hinged rope example?

    http://dl.dropbox.com/u/1027218/phystest.cap

    Also I can't search for a common word like physics so if they are other threads about this,I can't see them

  • Sprites can have animation frames with different hotspots,so you can cycle a sprite with your predetermined hotspot

    You can also set up multiple image points for position

    Also numpad 5 will center the hotspot/imagepoint right in the middle

  • Can't you just check it with the previous tick angle?

    Why do you need to see the future? as seeing the future can be complicated depending on the case

  • That's strange as your gpu does support 8192x8192 textures(well yours anyway) so in theory it should work

    Just what type of image are you trying to process anyway?(might help to give some point as to spread it out)

  • RaymondHooks

    I don't know about your problem but if you think it doesn't run well post in another topic or even further detail it here if you think its related

    However in Skyhunter case, the problem is most likely the hardware limitation and if so it has nothing to to do with software

    Skyhunter can you post what your gpu is?

  • "mmf2 imports large images ... without hardware acceleration"

    The point is that because it is hardware accelerated, you are constrained by its limitations

    For titling the image use grid alignment

  • Link doesn't work

  • Does your gpu even support 8192x8192 textures?

    First of all why would you have 6400 x 4800?you'r probably doing it wrong!

    Second if you must have that image at that resolution then split it up into parts

    Also be carefull about you vram which is your gpu memory!

  • > it is not global.Value('indexlevel') it should be this global('indexlevel')

    > because when you put a " . " at the end of a global you are in indicating that it is an object.

    >

    > I am assuming that you don't have an object named global at all and you are trying to use global Variables from the picture.

    >

    Holy crap, that was a serious brain-fart. I knew better than that. That's why I shouldn't stay up until 4 am working on things, thanks.

    When in doubt about the expressions just check the expressions with the objects at the bottom as they have all of them(especially system which has the math), if you don't have find the expressions in any of them that means that you have to create the appropriate object