No, it is not a pragmatic option. Nobody with even the slightest insight into how game development works is asking for what you're providing. Why use C3 at all if we're just slapping three.js into it? At that stage, Construct provides exactly zero benefits. Your statement around it not being easily possible is, at the most charitable reading, wildly disingenuous - because it's already been done. Repeatedly. For years. With three.js!
What has been asked for are a handful of things in SDK v2 that 3rd-party developers can use to create an INTEGRATED way to include 3D content that doesn't involve the hacks they've had to do that you're actively trying to prevent them from doing in SDK v2, making v2 come off more as the efforts of a control freak to prevent progress, not make it easier, officially supported, or remotely useful for those same 3rd-party developers v2 is ostensibly being developed to support. 1 step forward, 50 steps back.
3D could already be done this way in C3. It's the opposite of integration and more like sticking a piece of paper between 2 other pieces of paper.
"Debug Project" would be a welcome addition to the new preview functionality.
While it may be easy to convince a community made mostly of inexperienced devs that the solution is for multiple multi-billion dollar console developers to support the whims and obsessions of small engine developers in their platforms, the reality is it's their platform. You play by their rules, or you don't play at all. End of story. Anything else is delusional thinking at best.
Please explain to me how this is a driver issue:
imgur.com/a/VH5DvzA
So, here's the thing.
If all other software is working, including other software built upon the same tech to render graphics, but one piece of software is not? That's a software issue. Even if, from your POV, you've done everything by the book. Pretending workarounds, finding other ways to accomplish the same output, etc aren't part of software development doesn't help anyone, most of all paying users.
Ashley... if your update is breaking GPU drivers (in my case, nvidia 3080) for paid subscribers, it doesn't really matter if your changes are technically valid or "correct." You've still broken GPU drivers for paid subscribers.
This is a not complex thing to get.
I've been having the same issue and haven't updated any drivers, applications or OS. Totally locked down, no updates.
Above a certain size the canvas (and preview) will render black. Collision shape outlines are still visible but nothing else. I believe issue started occurring during the last beta cycle. My workaround has been to keep the search window docked under the canvas window to control the size it's drawing at.
The issue occurs with no other software, browser-based or otherwise.
The mutliplayer compression would be nice to use outside of the official multiplayer functionality, so we could also use it with other services, eg. Photon, for those of us who need a more reliable and remotely managed multiplayer backend.
Ashley
New issue related to your update related to search now that it follows the standard behavior of selecting the previously-entered text in the search field (thanks for that) - if the text/textbox is currently active and the user hits Ctrl+F again, it brings up the browser search field.
There's nothing to provide in an official bug report - just launch C3 from either the browser or desktop link directly and hit Ctrl+F a couple times.
The updated search functionality is useful, but when searching a second time using Ctrl+F, standard search field behavior is to select the pre-existing text to more quickly change the search query.
Try it in Chrome and you'll see what I mean.
Are you still updating this addon? It causes errors in recent releases.
Very, very, very few "big" games use Construct. Out of those, even fewer use the C3 runtime due to its limitations. This is a willful misrepresentation.
- Makes game engine, sells it as "no coding needed"
- Says will demonstrate game engine using coding, instead of all the things built-in and sold as positives to avoid coding, claims will prove power of engine
I'm sorry, what?
When creating an object with the Water behavior during gameplay, after resizing the object all that is visible is the water effect at the object's original size.
For example, create an object taht's 64x64, resize it to 128x64, the visual appearance stays at 64x64.
Is there a way around this?
Member since 21 Aug, 2013