Chadori's Recent Forum Activity

  • Voted. Good Game!

  • Well, it was worth a shot.

  • <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing"> Did anyone notice the new google chrome browser update on opening your browser lately? At first I thought it was a malware like the chromium browser. Good thing it wasn't. As confirmed here: https://productforums.google.com/forum/ ... G1PukcAgAJ

  • FaeDine - UID's normally don't duplicate, when the object is destroyed it's UID isn't reused.

    Maybe you used IID which is reused when an object that used it is destroyed.

  • ErekT - As I mentioned yes it won't consume as much but it is still dependent on the image size but as I also mentioned it is still using graphics memory regardless if it's invisible, sized (0, 0) as long as it is pre-loaded on start of layout.

    It's not a need but as I said, using memory for non-visual purpose is kind of wasting resources even if it is only a little bit. And as I also mentioned above without this feature there are chances of producing beginner mistakes relating to behavior boxes.

    If you read the whole thing you'll know my point.

  • It's not a really a need but having this really in a game engine does makes sense.

    Design:

    A Blank Object is just like a tiled background / sprite that isn't visible on export / preview but visible on edittime. It has no image or graphical content. You can change it's opacity / color / angle / and other basic properties. But again, it isn't really drawn on screen or anything. It is just there for behaviors.

    Purpose / Use:

    • Main Purpose : As a behavior box! For example:
    • As a Camera Box
    • As a Solid Box
    • As a Jumpthru Box
    • As a Platformer Box
    • For Calculations from Point A to B without using any graphic memory.
    • There are many more but you get the point.

    This is just like a Rectangular Box Tool, Line Tool or Ellipse Tool but not necessarily a line tool or ellipse tool. A Rectangular alike Box Tool is fine.

    Why need this:

    Point 1:

    It's really doesn't have any performance impact or anything but it just seems right having this. Especially for beginners.

    I remember the time that I didn't use a Behavior Box on my first game, I was a fool. I used the Graphic Sprite for the behaviors and

    i experience several glitches and at first I thought it was the code. So after 8 months developing my game, i realized my very big mistake.

    I should have separated the behaviors from the graphic sprite. I actually knew about it, but I thought the glitch was just by chance and could only

    happen on bad use of events.

    My point is that if we have this kind of feature intended for this purpose. Then there will be less beginner mistakes.

    Point 2:

    It's kind of like a bad practice to use graphic memory for something that isn't even going to be shown like behavior boxes or solid grounds. And in some cases. there are beginners that can make a very inefficient mistake. How do I know? Well it's because I myself made the same mistake.

    Some of the possible mistakes that can happen with beginners and can be avoided with this feature:

    1) Making a solid ground . Some beginners make a mistake when making a solid ground. Some make a single black colored sprite that sizes (1000,8), (8,1000) or any size that covers the part that is intended to make solid. This makes a huge impact on performance. Imagine the size! But this is unlikely to happen though .

    2)But making a sprite that has a size of (128x128) with a single black color for a behavior box. Now, this is likely to happen. There is now a little wasted graphic memory.

    3)Adding the solid behavior to the ground using connected separate sprites that are adjacent to each other. Now this one has a bug with IntelXDK that produces seams with solid behavior sprites adjacent to each other. So if any beginner does this without testing on IntelXDK first. Then it's game over . Time to redesign the game.

    4) Making a single black colored tiled background as a solid ground. Now there are cases when a beginner fills the default (250x250) tiled background with a black color without resizing it to (1x1) or (2x2) first. Then there will be a little bit wasted resource.

    I'm not saying it is a need, responsibility or a negligence of construct 2. As a matter of fact it is only optional for Construct 2 considering it's design and it is the beginners fault that they didn't read the manual if those mentioned above happened to them considering all the tutorials and documentation provided. But having this feature will make adding behaviors more comfortable for the users.

    But I got to admit though, this will make a huge change on Construct 2/3 tutorials about adding behaviors.

    Ashley , I hope you consider this feature request . But it's also okay if you implement this later on C3.

    Lol. I wouldn't dare using Unity2D for 2D games. That's just making life more difficult. But 3D is another story.

    I'm not surprised that there are so many bugs since the program is code-based and there are many possible outcomes in a single function.

    The program itself gives you the freedom to mess up.

    But I'm sure some are false bugs too from beginners like here in C2.

  • 2016 and I still +1 .

  • No, don't rebuy just yet, that's unfair. Go email Tom at to discuss your issue.

    I'm not sure if you can convert it to the website version & I doubt that it is possible but only think of rebuying after you have discussed your issue with Tom . He replies within 24-hours.

  • Cipriux - Ohh, yeah. I forgot about that. I don't use that so I didn't remember. Thanks

  • Problem Description

    Okay, first I made a general discussion before asking if anyone has experienced sudden change of active layers or objects changing z-orders / layers unexpectedly.

    Here: viewtopic.php?f=146&t=181112&hilit=+layer

    It happened to me unexpectedly for a long time, I believe more or less 6 months. I always encounter this bug and don't know the reason until now.

    This is actually annoying if you drag & drag objects from your projects bar in a fast pace which I do while I'm in a hurry.

    At first I thought it was a glitch that happens when C2 refreshes after a task but I was unsure & I now know that I was wrong, good thing I didn't make

    a bug report on that.

    Now, I'll explain the bug.

    1) The bug happens when you have a multiple docked document bars placed beneath each other.

    2) For example, A Layer Bar beneath a Project bar. (Remember to dock the Multiple Document Bars to the right, but regardless the bug is still produced. It is just for the higher chance of reproducing the bug since I have tested it already.)

    3) Make Sure the Project Bar is in front since it's pointless if the project bar is beneath since it doesn't have any obvious selecting features that reacts to the bug.

    4)Dock the Properties Bar to the Left Side to see the change of Layer.

    5)Add many layers, 12 will suffice. As long as the layer bar is filled with layers for higher chance of reproducing the bug.

    6) Now Select and Drag the Sprite to the Projects Bar but still hold the sprite.

    7)Move the Cursor up and down while holding the sprite.

    8)Now you will notice in the properties bar that the active layer is changing.

    Note: This also happens with the Z-Order, you can move an object to another layer with the bug

    Attach a Capx

    https://1drv.ms/u/s!AjcW2ueud6qp1H7h55ZGiYb5D7Yv

    Description of Capx

    It's explained above.

    Steps to Reproduce Bug

    1) The bug happens when you have a multiple docked document bars placed beneath each other.

    2) For example, A Layer Bar beneath a Project bar. (Remember to dock the Multiple Document Bars to the right, but regardless the bug is still produced. It is just for the higher chance of reproducing the bug since I have tested it already.)

    3) Make Sure the Project Bar is in front since it's pointless if the project bar is beneath since it doesn't have any obvious selecting features that reacts to the bug.

    4)Dock the Properties Bar to the Left Side to see the change of Layer.

    5)Add many layers, 12 will suffice. As long as the layer bar is filled with layers for higher chance of reproducing the bug.

    6) Now Select and Drag the Sprite to the Projects Bar but still hold the sprite.

    7)Move the Cursor up and down while holding the sprite.

    8)Now you will notice in the properties bar that the active layer is changing.

    Observed Result

    A Document Bar behind another document bar is still selected when dragging an object on it.

    Expected Result

    A Document behind another document bar should be locked and the user shouldn't be able to select any content on the covered document bar.

    Affected Browsers

    • Chrome: Yes
    • FireFox: Yes
    • Internet Explorer: Yes
    • Nw.js: Yes

    Operating System and Service Pack

    Windows 8.1 64-bit

    Construct 2 Version ID

    Construct 2 r235 Beta Release

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • erickson400 - Get the website version! Steam has a lot of bloatware that sometimes interrupts Construct 2. Construct 2 also sometimes crash / lag there caused by Steam related problems, that's just what I heard from the others though.

    It is better to have your program in an independent state than having 2 programs run just to open 1.

Chadori's avatar

Chadori

Member since 10 Oct, 2014

Twitter
Chadori has 49 followers

Trophy Case

  • 10-Year Club
  • Entrepreneur Sold something in the asset store
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • x2
    Coach One of your tutorials has over 1,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • RTFM Read the fabulous manual
  • x2
    Great Comment One of your comments gets 3 upvotes
  • Delicious Comment One of your comments gets 10 upvotes
  • Email Verified

Progress

24/44
How to earn trophies