R0J0hound's Forum Posts

  • The mouse isn't setting the angle, it's setting the target (or the location to arc to).

    To target a different object just replace "mousex" and "mousey" with the object's x and y.

  • That's higher end than all the computers I use, It should run Construct just fine.

    In fact I would venture to say that Construct will run fine on any new computer. The only time you'll dip below the minimum system requirements is when using a much older computer.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Here is one way to do achievements:

    http://dl.dropbox.com/u/5426011/examples4/acheivements.cap made in 0.99.97

  • There is no list other than the script editor.

    You won't be able to get OnCLick to work because it's a trigger. Any condition that is a trigger (or has a green arrow to the left in the event editor) will not work in python.

  • You can do it with one event with the physics behavior. Change the PV 't' to change how long in seconds it takes to get to the target.

    http://dl.dropbox.com/u/5426011/examples4/projectile2.cap made in 0.99.97

  • I created a python script file and named it rightarrow.py.When i try to load the script on the event's

    page then it just shows nothing.Was the open py file in the editor just an afterthought?.

    Saving and loading in the scripting editor are not currently implemented.

  • Your array editor looks like it's saving the values as text instead of numbers. It shouldn't make much of a difference though as construct easily converts text into numbers.

    However you will run into an issue when you try to add two array values together and they are both text. The text will be concentrated together instead of added numerically. The solution is to convert the values to integers with int().

    Ex:

    Array(1,2)="10"

    Array(1,3)="11"

    Set Text to Array(1,2) + Array(1,3)

    // Text will be "1011"

    Set Text to int(Array(1,2)) + int(Array(1,3))

    // Text will be "21"

  • Downloaded it again, it works now.

    [quote:lzv1n7mi]However, what if I had to use MFC? How do I know what the end user's system requires without using the "Use MFC in static library" and getting a 2MB plugin?

    For checking what dlls a plugin uses I use http://www.dependencywalker.com/. I don't have a solution for the mfc problem. My idea would be to use older mfc dlls that are always included with windows, but I haven't looked into how that could be done.

  • It would not load for me. I checked the dependencies and it looks like it needs: MFC100D.DLL and MSVCR100D.DLL. You should be able to eliminate those dependencies in the solution properties and tweaking the "Use of MFC" setting, or you may want to try to switch to the win32 template in the sdk.

  • It doesn't have a name. You can use just "LoopLength" without the parenthesis to get the current loop length.

  • If you move the "Infinite movement" group above The "BouceStar" group the collisions are spot on.

    I think the issue was the ball's y position was being set after the collisions were detected, and it wasn't quite lining up with your logic.

  • I believe the plan is to allow the creation of exporters to any platform.

    From the FAQ:

    [quote:3ityeret]Q: What are these exporters I'm hearing about?

    A: Exporters compile projects into various formats for use on different platforms. This time they are modular and can be made by anyone, just like a plugin.

    Q: Why is HTML5 the main exporter?

    A: The HTML5 exporter is being made first mainly because it is multiplatform. Having immediate multiplatform support is meant to attract as many users to C2 as early as possible.

    Q: Will there be an EXE exporter?

    A: Yes, eventually. Either the Scirra devs will make one, or a third-party will make one. With the modular exporter system, it could be both. By the time C2 can be used for much, there will probably be an EXE exporter.

  • If you post the cap, someone should be able identify if it's a bug or logic problem. At least it's the easiest and fastest way to get a solution.

  • The correct syntax would be, Player.Overlaps("Sprite3"), but "Overlaps" will cause a crash when used in python because it's implementation requires it to be attached to an event.

    A solution is to use Player.OverlapsOffset("Sprite3",0,0) instead.

  • The names will be changed for the next build.

    "Set Zoom" will be "Set Zoom Rate".

    and

    "Set Zoom Offset" will be "Set Zoom".