Posts by MPnetbox

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    I just finished fixing your application and is now submitting the data to the server. I even fixed the single quoting issues so that it won't break the sql query.

    Please login to see this attachment.

    Hope that this will fix all your submitting issues ;)

    Thanks guys. It's not the CORS thing - tried that.

    I also replaced the code with MPnetbox suggestion, although now data doesn't seem to post from android or PC.

    Someone must have got it working as there are four entries in my database ("double quote test", "working on mobile device") etc (assuming that was MPnetbox) I'll keep trying though!

    Those were my entries using my phone, so i know that it was working (except when using the single quotes because it would probably break the sql query)
    I will take another look into this and i will reply in a few minutes with the working example.

    I just tried your application and realized that the values passed to the url from the combo boxes and text should be URL encoded, or else you will have problems on android.
    Special characters like space have to be converted to %20 for example...
    This could be easily fixed by using the GET object function called URLEncode$( "Get object", >The text from the inputs<)

    Your URL should look like:
    "Please login to see this link." + "?name=" + URLEncode$( "Get object", Combo Select$( "Combo Box" ) ) + "&school=" + URLEncode$( "Get object", Combo Select$( "Combo Box 2" ) ) + "&worklog=" + URLEncode$( "Get object", Edittext$( "Edit Box" ) ) + "&time=" + URLEncode$( "Get object", string$( "Time" ) )

    Replace the fakedomain.com with your server domain

    You will still have some issues with text using single quotes... you should convert the single quotes character by using the html equivalent code ( ' ) just to be safe and prevent some hacking attempts.
    I did not test it, but try replacing ' with '
    You can use the String Parser object for this and you should use it on the Edit Box value because this is the only field with custom values from the user.

    It might be better to move the camera only when away from a certain distance. Its kind of the reverse of what it is doing now.
    If its X or Y pixels away from the center it should slowly track the ball, otherwise the camera goes back to the center.
    But without seeing the actual game running, i'm just guessing that this way is better.

    Try this example:

    Please login to see this attachment.

    It's not using trignometry to do any radious limit, but i believe that it's probably good enough.

    The camera tracking limit is calculated relative to the CameraObject Active, so this way you can position it where you want.

    There's also some variables that you can customize:
    - speedX
    - speedY
    - maxDistanceX
    - maxDistanceY

    All other variables are calculated automaticaly, so there's no effect on changing them manually.

    If you really must use a radious limiting i can try to do that, but my math skills are not that good so it will require some effort.

    Don't know if this will work, but try to right-click your CF executable and go to properties. On the compatibility tab, there's a checkbox for high dpi screens, try checking it and execute the software.

    On windows 8 i had to check this option on several programs because it was causing some blurring that i did not like. Maybe windows 7 also has that option too.

    Unfortunately, after a lot of attempts, i'm afraid that i can't come up with a better solution for your problem. There is always one issue here or there...
    I can't guarantee this, but i think that you will probably have to cut your actives to the size of individual cells, otherwise buildings with irregular cell count will always have a problem at some point.
    I'm all out of ideas right now.

    I never tried to make an isometric game, so i might be a little far from the best way to do this... but my approach would be:

    - Place the action point on the center of the isometric base. Something like this (X marks the spot... or action point :P ):
    Please login to see this attachment.

    - To make sure that all my actives are with correct positioning, i would also create a photoshop template (or use other software that uses layers) for each kind of cell positioning.
    This way i can position the sprite easily on the center and when exporting to png i would just hide the guidelines.
    Check the attachment for a PSD template.
    Please login to see this attachment.

    - Finally import the png on CF and center the action point (do not use the center of mass). To avoid extra blank space, you can just click on the crop image.

    I created a modified version of your mfa so you can check it out.
    On this example i never cropped the images so you can understand a little better how i exported the png. You can crop them later on CF.
    I also created an option to create objects on the fly... just click on your keyboard from 1 to 4, then click on the left mouse button to drop an object.
    All objects are snaped to a 8x8 grid.
    If you see some weird overlapping, it's because the objects were created with a wrong placement... i'm assuming that overlapping cells will not be allowed in your game.
    If you are not using some sort of snapping to avoid overlapping, i think that you can't prevent those problems because the actives are not real 3d.

    Hope this can help you out.
    Like i said before, this would be my first approach... i don't know what other issues i would encounter later so don't take my word for granted that this is the best method available.
    Maybe someone with more experience can give better advice ;)

    Not really sure if this is the case, but probably you antivirus is causing that problem. Try to disable it temporarily and run the frame again. If that's the case you must create an exception on your antivirus to ignore it.
    For example, avast activates sandbox mode the first time you try to run a frame on CF and cause an error until it finishes analysing and making sure that its safe to run.

    It seems like there's a new version every week, yet Steam users are still stuck with 283.5. Any ETA?

    Version 284.5 is available for Steam users as Beta. I'm using it right now.

    Please login to see this link.

    To enter the beta test:
    - open steam;
    - open your software library;
    - right click on your Clickteam Fusion and select "properties";
    - open the "Beta" tab and insert the key to gain access to beta ( x243TNkwZS1239 );
    - You can revert back to 283.5 at any time by opt out of the beta testing.

    Hope this helps

    I'm testing the Steam beta version of CF2.5 and when building my app for android device i'm facing some problems with the "fit outside" display mode.
    It looks like it's not really resizing, but just behaving like the "Center" display mode.
    All other display modes looks like they are working just fine.
    This also happened on 284.4 beta version.
    On 283 it was working fine.

    To make sure that it was not an issue with a previously created application, i created a new one from scratch and had the same issue.
    My frame and app size is 640x960. Tested on my HTC One X and on Nexus 7.

    Is anyone else having this issue, or is there something else that i must change on this new version? Sorry if this problem was already mentioned... i searched on the bugtracker but didn't find anything related to this.

    If anyone want to test, here is a simple MFA with this problem. Just build and run on a android mobile device. It should be fullscreen instead of those green borders.

    Please login to see this attachment.