tarek2

Here's a capx I did that has 160 in layout and checking distances between everything on screen very low CPU usage. The trick is to use nearest, you dont have to check distance of every single one every tick. if the nearest one is not even within range there's no point to check all the rest of the instances either.

Hope that can help you out.

https://www.dropbox.com/s/3mc7dmbnfs8o8 ... .capx?dl=0

tarek2

16 objects doesn't sound like a lot. Care to explain how it works?, maybe I can come up with something more efficient in your case.

Are they all checking distance too eachother and get picked if colliding?

Maybe just a Trigger once while true will help?

Otherwize it could probably trigger the jump every tick while Y is more than 0.

in case the analog is not 100% accurate it may be better to raise the value as well.

Gamepad: Gamepad 0 Left analog Y axis < -10 or something?

Ashley

Awesome news. I will join the edge bug hunting after the official creators update though, as I have too much important work related stuff on my computer so not very comfortable running insider preview.

I'll probably mostly look for bugs related to working with touch and pen as main input, as I'm a couch developer :p

do you know if is possible example you have 20 objects on the screen the idea is to take the UID of all those 20 objects and just loop between them checking distances between them and depends the distances do some actions those objects, is it possible without looping through the whole 150 instances that are not on the screen

Forgot to answer this one.

For this you can just use the "is on screen" condition. I think that's the best way to shortlist.

Sprite is on screen

check distance

That way you first pick only the instances that are on screen, and then you can run your distance calculations on just those.

> I don't know if this work for you, but I sometimes use dictionary to store picked UID's. That way the for each loops doesn't have to loop through a whole family, but only the ones stored in the dictionary. That might work when you have many units in the same family, but let's say 20 out of 100 selected, as you don't have to loop through the 80 that are not selected. I found it to have some performance benefit in some cases.

>

> For me the picking itself seems to use a lot of cpu in some cases, so i try to find ways to use some more lightweight way of picking objects. Restructuring the condition order can help a lot too.

>

> For example:

> For each unit (loops through all units)

> is Selected. (then picks and filters the ones selected)

>

> insead use.

> Is selected (pick the selected ones)

> For each unit. (loops through only the selected ones)

>

> Small things like that can help a lot, but you probably know that already. Trying to filter down with conditions as much as possible before running any for each loops and actions, seems to work pretty well in most cases.

>

Hi tunepunk I show you did an interesting test on this how-do-i-pick-multiple-by-uid-string_t190930 very good test Thanks

Did you manage to find any good results or ways how to improve ?? I will be very interested in that

do you know if is possible example you have 20 objects on the screen the idea is to take the UID of all those 20 objects and just loop between them checking distances between them and depends the distances do some actions those objects, is it possible without looping through the whole 150 instances that are not on the screen

In some cases i found that using LOS behaviour could be a bit better, it's pretty much a range check as well, if you set a 360 cone, and they can also utilize the "use collision cells" option.

Another way that is way less CPU intensive is to use pick nearest/furthest, if something is within the range you set a boolean, and loop through that a few times per tick. It updates slowly but uses less cpu, so can be good for something that doesn't need to be instantly updated, or if you have a lot of instances but most of them are outside the viewport, in other areas of the layout.

Code looks like this:

Edit: Added link to C3 project.

https://www.dropbox.com/s/96e7y0njoqyqd ... e.c3p?dl=0

I don't know if this work for you, but I sometimes use dictionary to store picked UID's. That way the for each loops doesn't have to loop through a whole family, but only the ones stored in the dictionary. That might work when you have many units in the same family, but let's say 20 out of 100 selected, as you don't have to loop through the 80 that are not selected. I found it to have some performance benefit in some cases.

For me the picking itself seems to use a lot of cpu in some cases, so i try to find ways to use some more lightweight way of picking objects. Restructuring the condition order can help a lot too.

For example:

For each unit (loops through all units)

is Selected. (then picks and filters the ones selected)

insead use.

Is selected (pick the selected ones)

For each unit. (loops through only the selected ones)

Small things like that can help a lot, but you probably know that already. Trying to filter down with conditions as much as possible before running any for each loops and actions, seems to work pretty well in most cases.

From what i understand, that should probably be possible when they release a standalone version. I don't know how far off that is in the pipeline, but they said it's coming. I'm also not a fan of working in the browser always, mostly because the file handling is clunky. So let's hope the standalone version comes soon

- Is there a way to set "Expression dictionary" to be opaque at all time?

It's very frustrating to watch it constantly change transparency while you move your mouse around.

- is there a way to keep the size of "Add action" window?

I like to resize it so I can see all the possible (at least default) actions without scrolling around. Right now every time I want to add an action, for any kind of object, the "Add action" window shows up always in default size and i need to resize it manually.

- Preview, debug.... button on main screen. Is it possible to make them all visible?

There is only a "Preview layout" button and a little arrow to press on to show more options. It would be nice to be able to customize it to show more then one button.

I understand that some of them might be actual feature requests, but I want to ask first.

1. It used to be that way but someone suggested it should fade like in C2, i prefer to have it opaque also, so hopefully Ashley can add a setting for that? I also find it a bit frustrating.

2. I'm with you there also. It would be good if C3 could remember sizes and positions. File bug for it...

3. It used to be that way as well, I have no idea why the insist on hiding stuff in submenus, it's quite annoying. You want stuff you use often to be easily accessible.

michael

Hooray!!!! That's Awesome news!

Well, chrome and other browser might be first in terms of new technology, always adding new stuff, but often breaks or very bugged. But edge is a bit late in that sense but they usually get it right, not rushing new untested features to the masses. At least that's my impression. Many chrome releases broke a lot of things for me, especially things related to touch/stylus input. I'm mostly working on a surface pro 4, often using the pen, so it's important that works for me.

I think the the stable autumn creators update is not far now... I might test it then.

michael

That's great news, thanks for investigating. I'm always a bit weary about running the insider preview builds. Have done before and had to roll back and reinstall everything, a few times.

So it seems like we could be running C3 in edge quite soon then. I really hope so, as I'm not a big fan of Chrome at all (especially since their touch/stylus support isn't very great), so I'm still sticking with C2, until i can run it in edge.

Did you try changing the settings in about:flags?

There should be a setting to use edge canary, and also a toggle for using experimental javascript functionality, maybe that would solve some of the issues?

I don't see why not, unless there is something technical keeping you from using it.