TheLure's Recent Forum Activity

  • The monitor tools that are causing this problem are luckily not part of the standard drivers. It's extra software you need to get from nvidia so this will luckily only be a issue for people that have manually installed this extra nvidia stuff.

    On a side note: The monitor tools are actually quite useful to monitor and log stuff as you can monitor lots of system values, not only graphic card related. It can also log to a text file. But possibly nvidia don't keep the monitor software up to date with their own drivers. :P

  • Just to add some mote info:

    There are some strange graphical issues in the layout view in Construct showing when I have any of the nvidia monitoring windows up. They go away if I just hide the nvidia windows (app still running).

    When I first start Construct and the tools are running it looks like this:

    http://dl.dropbox.com/u/44294994/Construct1.PNG

    Then I use the keyboard shortcut to hide the nvidia screens (ctrl-alt-s), click in the layout view and it looks normal:

    http://dl.dropbox.com/u/44294994/Construct1b.PNG

  • I have the latest driver (according to nvidias update service).

    I guess not much can be done but at least this is searchable here if someone have a similar problem. Simply closing the nvidia system monitor before starting Construct prevents the problem.

    Construct is the first software to suffer from it though but on the other hand I don't runt much software on this machine.

  • Hi

    I have not played around with contruct for the last betas but when I updated to R70 today I ran into huge problems: Construct crashed everytime I tried to create a new project. So I uninstalled Contruct, made sure the registry folder was gone and reinstalled R70. There's a different behaviour now but the crashes seem to be related to creating/loading/opening/saving projects and/or layouts.

    I have made one change since I used Construct 2 last time and that was installing the NVIDIA System Monitor tools. And sure enough, if I close NVIDIA System Monitor Construct seems to be working normal. Running MVIDIA System Monitor causes Construct to become completely unstable and crash to desktop without any error but the normal windows "aplpication stopped working" exception error.

    Some kind of conflict related to using hardware accelerated graphics?

    I'm running Windows 7 64 Bit.

    My Nvidia drivers are 285.62 and I'm running a GTX 460.

  • Very cool! Simple but entertaining.

    Not sure if it's a "feature" but you could try to improve the way win/failure is checked so that you don't get a "you win" message even if you lose later because you're slowly rolling off the platform and falling down several seconds later. :)

  • Sweet! I had actually missed the sprite pack completely. :)

  • Forgot to add:

    Mostly a actual error/crash of some kind is much better then silently ignoring a error. If array don't like float values for X, Y, Z I would much prefer if the runtime crashed when you try to use a float value. It's like creating a try/catch statement and then just leave the catch statement empty with no error handling = bad.

    Edit: Ah, you CAN edit. :p

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I think I found the issue:

    I was using random() when getting and setting values in the array... random returns a float value and it seems arrays accept them but then you just get weird or "blank" results... no errors or anything. It seems you have to keep this in mind when using arrays.

  • I wanted to try out Arrays so I created a new blank project (r60). On the start of the layout I'm trying to create a array by first setting the size and then i have a sub-event with a For each XY element that sets the value at CurX and CurY to 10+Random(5)

    The above seems to have no effect. Nothings happen. It seems like all values in the array is 0... I'm not even sure the For Each XY element part is running at all...

    What am I doing wrong? Or are arrays bugged in R60?

    My project:

    dl.dropbox.com/u/44294994/room-test.capx

  • Not sure if this is a actual bug as much as proof that the collision polygon auto-generation feature on sprite image import is not done yet, but importing this picture:

    <img src="http://www.thelure.se/C2/Bugs/flag1.png" border="0" />

    results in a complex polygon like this:

    <img src="http://www.thelure.se/C2/Bugs/flag1result.png" border="0" />

    Are complex polygons ok with the collision system?

  • TheLure: the link to your capx isn't working. Is it in the public folder?

    Agh, there was a space hidden in the end of the URL and I cant edit the post.

    Here it is again

  • I used CustomMovement to create this effect.

    I made object variables for the player target X and Y. When the mouse is clicked I set target XY to the mouse XY.

    Then I just compare the players XY against his target XY and if they differ I turn the player sprite towards the target XY and give him some acceleration.

    When players is near the target XY I stop the movement.

    Example capx here

    I guess you can use bullet behaviour also the same way.

TheLure's avatar

TheLure

Member since 18 Sep, 2011

None one is following TheLure yet!

Trophy Case

  • 13-Year Club
  • RTFM Read the fabulous manual
  • Email Verified

Progress

15/44
How to earn trophies