Valhallen's Forum Posts

  • Hello,

    I am working on a game that looks like a little gameboy console in the viewport, with controls at the bottom and the game window at the top.

    I have created a non-parallaxing UI, but I'm not sure how to get the game working within a smaller portion of the viewport with respect to behaviors like ScrollTo, etc which use the full viewport size when deciding when to scroll.

    Is there a way to create the playable game portion in a small square viewport, and then add the console frame and controls outside of it without expanding the actual game's viewport? I guess I need like a viewport within a viewport, if that makes sense...

    I imagine this might be possible by exporting the game in the small square viewport and then adding the control frame around the game in HTML or something, but I'm not sure if that is the best route for testing and development etc.

    Any suggestions or tips are welcome.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I recently bought a new iPad Pro, and was curious about the possibility of doing some semi-serious Construct 3 development on it. So far I've run into several quality of life issues that interrupt my development flow and prevent me from wanting to use it further.

    I figured it would be productive to report these issues, and hopefully they can be ironed out in time. Some are touch-related, others are general usability issues. Not in any particular order.

    I'm using Safari, and saw a few additional issues with Chrome and Firefox, so I just stuck with Safari for my testing.

    • Expression suggestion list not scrollable using touch
    • Current color not visible in sprite editor without opening panel
    • Expression functions added using autocomplete do not have parentheses
    • Reordering/reparenting events on touch screen is tedious. Revolves around longpressing & clipboard operations when it could be drag & drop.
    • Creating instance of an object is a long-press option, could be drag & drop from project panel.
    • Sprite editor brush hardness/opacity values < 1 create noticeable banding in the brush.
    • Background color property of Project Properties panel does not appear to be editable.
    • Lots of strange issues when attempting to scroll various panels, often selects items instead of scrolling, one time made the whole website zoom instead of the viewport.
    • Having to swipe multiple times to expose the correct panel is tedious, especially since many panels are mostly empty space. Would much prefer dockable/tabbable panels or buttons.
    • The "Add Condition" windows and related action/condition windows allow interacting with the dimmed events sheet behind it.
    • Long pressing in side panels causes full-panel flashing & dimming
    • Side panels can be grabbed when tapping near the edge, without actually dragging horizontally, so long-pressing to open context menu and dragging side panels is possible in the same action.
    • The "Log In" window was not interactable when going from "Menu -> Login" or tapping on "Guest -> Login", had to click on "Guest -> View Details -> Log in to existing account"
    • Using the "add to home screen" option, Construct 3 was reloaded fresh every time it is opened, even if only backgrounded for a moment. Had issues connecting to Google Drive from the home screen version.

    I attempted to use the editor in the "Request Desktop version" in chrome, but soon found that the touch-scrolling of the website prevents proper drag & drop functionality in this mode, among other issues with touch input.

    Overall I feel that the tablet version of Construct 3 should look and feel more like the desktop version than the mobile phone version, especially in landscape view. With a good pass of touch-control related fixes and UX design, I think the tablet could be a much more viable full-time platform for development.

  • How exactly do you imagine this feature working?

    Ashley

    Currently to achieve a scrollable, typing dialog effect with multiple fonts or webfonts, I am using Rex's Typing, Scrolling, and TagText plugins and also Boundary for the scrollbar.

    You can see my end result here:

    http://www.thezeroreview.com/growth

    It was not elegant or simple to setup, but I think you could look a these plugins/behaviors as inspiration for a better way to integrate features into the editor in a game-agnostic way.

    Currently the scrolling is really cropping the lines of text in a buffer, instead of actually masking the text etc. It would be ideal to be able to mimic a true scrolling text field element as if in a browser perhaps.

    http://c2rexplugins.weebly.com/rex_text_scrolling.html

    http://c2rexplugins.weebly.com/rex_text_typing.html

    http://c2rexplugins.weebly.com/rex_tagtext.html

    http://c2rexplugins.weebly.com/rex_boundary.html

  • Yeah, I guess once you have logic, it's just a language to learn.

    Yes and no. Construct 2 is Javascript, and it lets you do whatever you want at any time. There's no inherent structure to it, and it's very easy to do something grossly inefficient.

    If you use Unity, you should use C#, period. Unity's Javascript is not actual Javascript as explained here: http://wiki.unity3d.com/index.php/Unity ... JavaScript

    So while the logical aspects will transfer over, you still must learn Object-Oriented programming techniques to really succeed. Unity is a component-based system and to make the most of it, you need to understand concepts like inheritance, polymorphism, encapsulation, abstraction, and how to use a strongly-typed api.

    So while you can use the language and create things in a Construct-esque way, your game will suffer for it.

    Unity is also a 3D engine, so you have to think about the Z axis even when doing a 2D game.

    That being said, I find Unity to be an amazing tool for learning C# (i learned all the C# i know through Unity, and now work full time doing it), so I sincerely encourage the foray into new engines and new languages.

  • You can lock entire layers from the layers panel.

  • rexrainbow That appears to have fixed my issue.

    You can see my project here: https://www.thezeroreview.com/growth/

    I must have used 9 or 10 of your plugins to create this.

    The fix will not be pushed until the next website update.

    Thanks so much for your patience and work! Truly fantastic.

  • rexrainbow

    Sorry for the delay. I've been very busy the last few weeks and forgot to respond here.

    It would appear that if the string already contains a newline keyword, this error occurs.

  • rexrainbow

    Yes but I am away from my computer for the next few days. I will post here when I return, thanks.

  • rexrainbow

    Strange, your sample works perfectly fine, but my game crashes when I enable the new property.

    Do you know what might cause an error like this?

  • rexrainbow

    Yes, I understand. Thanks anyway, keep up the great work.

  • rexrainbow

    I figured it had to be something like that, or you would have implemented it already. Thanks again, I appreciate the response!

  • Yeah I'm feeling the same way. Lots of quality of life improvements and surface level improvements, but it's the same engine. Most of these updates could have, and should have come to C2 long ago.

  • rexrainbow

    I have a question/request regarding this behavior.

    I've seen this discussed elsewhere so you may have already considered this, but would it be possible to implement an option for the typing behavior so that if a word will wrap, it will automatically push the text to the next line before it begins typing that word?

    I currently have your TagText, scrolling, and typing text plugins/behaviors all working in tandem flawlessly, but the jump when a word wraps mid-type makes it just shy of perfect in my eyes. I do not know how feasible this is to accomplish, so no worries if it's not in the cards.

    Thanks again for the fantastic plugins and support. I would not be using Construct 2 for my current project if not for your hard work.

  • rexrainbow Just tested the new version and it works like a charm. You are a gentleman and a scholar.

  • Hello rexrainbow, big fan of your plugins.

    I discovered an issue while using TagText and also possibly typing (?) so I wasn't sure which thread to post in. Since the stack trace leads to TagText, I'm posting it here.

    It appears that if a <class=''> tag is separated from it's closing </class> tag by a 'newline' keyword, the plugin will error if you try to call the "Type Text" method.