UPBGE 0.3 - Some feature requests for logic bricks #1496
Replies: 14 comments 3 replies
-
|
Add the option of using a property as value for Property actuators For operations like adding and subtracting, it would be very useful to be able to use a property instead of a typed number as Value, so you can use the current value defined in the property, instead of a fixed one. Example: I want to add 'ammo extra' to the 'ammo' amount, but 'ammo extra' is defined in another object (needs to be copied) and can change over time. So instead of a number we would set the property itself as a value for the add operation.
PS: This could also be useful for other logic bricks, like Property sensors, for several operations, like the values for Intervals, Greater and Less than, Equal, etc. |
Beta Was this translation helpful? Give feedback.
-
|
"actuator use property"
I actually had this request before - it's a good one,
when coupled with 'sensor set property' - it makes the logic bricks as
strong as nodes
…On Mon, May 31, 2021 at 9:04 AM arch-sketch ***@***.***> wrote:
*Add the option of using a property as value for Property actuators*
For operations like adding and subtracting, it would be very useful to be
able to use a property instead of a typed number as Value, so you can use
the current value defined in the property, instead of a fixed one.
Example: I want to add 'ammo extra' to the 'ammo' amount, but 'ammo extra'
is defined in another object (needs to be copied) and can change over time.
So instead of a number we would set the property itself as a value for the
add operation.
[image: a06]
<https://user-images.githubusercontent.com/81666035/120218658-739f0a00-c210-11eb-924c-01eed0b3ef5f.jpg>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1496 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABW3SWJMCYKK4CV23U4B6Q3TQOXRDANCNFSM453D3MDA>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Indeed, it would definitely increase their versatility. |
Beta Was this translation helpful? Give feedback.
-
|
Update property name changes automatically inside logic bricks When a game property name is changed, it would be best if it could automatically update in any logic bricks using it. Right now it goes red, signalling there's an error, but you have to manually change to the new property in each brick where it is used, which can be time consuming for long logic trees, and also prone to mistakes and/or omissions.
|
Beta Was this translation helpful? Give feedback.
-
|
Add Comments "logic bricks" This one Im not sure what design would be best (I did make a quick mockup of one possible solution), but it would be very useful to be able to have comments inside a logic tree to document them, for explanations, annotations, visual clarity, etc.
|
Beta Was this translation helpful? Give feedback.
-
|
Allow for the scrolling or zooming of the editor window while holding on the connector link Right now when you are in the process of linking between two bricks, you cant zoom or scroll the editor window while holding on the link 'noodle', which makes it very awkward when the logic tree cant fit entirely inside the window area. You are forced to zoom out and have both bricks in view before connecting them, which is a problem when the logic tree is long. It would be very useful to be able to still use the middle mouse button to scrool or zoom while holding the connector link with the left mouse button. Optionally, it would be also nice if the window could auto scroll if the mouse is near the border of the window, while holding.
|
Beta Was this translation helpful? Give feedback.
-
|
Use Properties as input values for sensors and actuators Elaborating a bit on what BluePrintRandom mentioned and the request above, it would be extremely useful to be able to use the current value of a property as input value for sensors and actuators. Not only in terms of convenience (editting a single value that will aplly to several logic bricks at once), but more importantly to allow for certain operations that require the input values to be read dynamically (in this example, the speed value could be changed during gameplay and the values updated accordingly).
|
Beta Was this translation helpful? Give feedback.
-
|
Make logic brick's names easier to read When organizing a logic tree, it becomes very important to name the logic bricks in a descriptive way. This often means that the names get truncated, since the name input box display area is very small. The only way to read them in their entirity is to hover the mouse on top of it and wait a second for the pop up info window to appear, with its full description. This however is only possible if your logic brick is already maximized. If its minimized, hovering over the name wont invoke the info window. While it would be great in the future if we could improve the design of the logic bricks to allow for more area to display the names (so you can read them on the whole logic tree at a glance), a useful alternative would be to have the popup info window appear when you hover the mouse on top of the names of minimized logic bricks (and not only when they are opened). This would solve the inconvenience of having to maximize each brick you want to inspect for its full name.
|
Beta Was this translation helpful? Give feedback.
-
|
Set direction for the mouse movement sensor We have a logic brick sensor to detect if mouse movement is true or false, but no way of specifying which direction we want to be detected. It would be great if we can add the same functionality we have for the movement sensor, to the mouse movement sensor.
So when we choose mouse movement, we can specify the axis, local/global and threshold |
Beta Was this translation helpful? Give feedback.
-
|
Add smoothing to the mouselook actuator Right now, the 'vanilla' mouselook offered by the actuator is lacking in terms of smooth movement. It feels rough, the flow is visibly jagged. Although there are ways of adressing this via python, It would be very useful to have a bult in 'smoothing' value added to the mouselook actuator. This would be useful for all beginners and non gaming users (archviz, teachers, etc) where it wouldnt be practical to develop or search online for a script in order to have a smooth looking mouselook.
|
Beta Was this translation helpful? Give feedback.
-
|
Add 'blendout' functionality to the action actuator Currently there's a lack of a 'blendout' function to allow for an animation playing on top (layer above) of another animation (layer below), to seamlessly blend back to it after being played (the same effect the blendin function does at the start). However, this feature does exist in blender right now, in the NLA editor.
It has the exact expected fuctionality, allowing for smooth blending of key frames at the start and end of an animation in a top layer (with the animation on the layer below). This seems like a very important feature to have built into the action actuator. I dont know if the existing NLA mechanics can be ported into the logic brick, but maybe it could be a useful reference.
|
Beta Was this translation helpful? Give feedback.
-
|
Add slow parent functionality (and possibly tracking axis) to the Parent Actuator Right now, to parent an object to another, we can use both logic bricks (on game start) or the blender native function (before the game starts). With the native mechanics, we can also set the tracking axis and perhaps more importantly, slow parent. But the parent actuator doesnt provide these options, which means we are lacking these mechanics for parenting relations activated inside/during the game. It would be very useful to have them added to the parent actuator as well, if possible.
|
Beta Was this translation helpful? Give feedback.
-
|
I believe you would want the track to actuator to handle tracking
another objects rotation or to rotate to face another object.
maybe a new mode 'lerp to other rotation'
best not mix the nodes purposes.
…On Fri, Aug 27, 2021 at 8:41 AM arch-sketch ***@***.***> wrote:
*Add slow parent functionality (and possibly tracking axis) to the Parent
Actuator*
Right now, to parent an object to another, we can use both logic bricks
(on game start) or the blender native function (before the game starts).
With the native mechanics, we can also set the tracking axis and perhaps
more importantly, slow parent. But the parent actuator doesnt provide these
options, which means we are lacking these mechanics for parenting relations
activated inside/during the game. It would be very useful to have them
added to the parent actuator as well, if possible.
[image: 01]
<https://user-images.githubusercontent.com/81666035/131153269-7013b6db-3bcf-42cc-97d0-a4f10b0ca0cd.jpg>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1496 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABW3SWP3APEKYWAIOX22UELT66WZBANCNFSM453D3MDA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Although that does sound interesting, I just think the in game parenting options are limited right now. You can remove a parent relation, you can set a parent relation (just object option, I believe). You cant set a slow parent with offset, for example. Again, you can do this "offline" in blender, but not when you parent objects in game, using the parent actuator, because it doesnt offer the options. |
Beta Was this translation helpful? Give feedback.
-
|
yeah, I believe slow parent is a good idea in parent actuator
however I think 'track other objects rotation' with defined up / forward
should be in the edit object actuator like track to is
…On Fri, Aug 27, 2021 at 10:17 AM arch-sketch ***@***.***> wrote:
Although that does sound interesting, I just think the in game parenting
options are limited right now. You can remove a parent relation, you can
set a parent relation (just object option, I believe). You cant set a slow
parent with offset, for example.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1496 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABW3SWLRJV3I7ZWWBAMWTKDT67CDBANCNFSM453D3MDA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
this would allow slow parenting to one object, but using the rotation of
another for instance./
On Fri, Aug 27, 2021 at 11:42 AM Jacob Merrill ***@***.***>
wrote:
… yeah, I believe slow parent is a good idea in parent actuator
however I think 'track other objects rotation' with defined up / forward
should be in the edit object actuator like track to is
On Fri, Aug 27, 2021 at 10:17 AM arch-sketch ***@***.***>
wrote:
> Although that does sound interesting, I just think the in game parenting
> options are limited right now. You can remove a parent relation, you can
> set a parent relation (just object option, I believe). You cant set a slow
> parent with offset, for example.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#1496 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABW3SWLRJV3I7ZWWBAMWTKDT67CDBANCNFSM453D3MDA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
Beta Was this translation helpful? Give feedback.
-
|
Indeed, youle made it possible to use blender's constraints in game by using the 'override logic transform priority' function in the object properties, but the drawback is that you cant use other logic bricks at the same time, they are ignored. So you are limited to either using the constraints or using logic on an object, not both. It would be wonderful in the future if the constraints were to be fully integrated into the realtime environment (like the bone constraints are), which would allow for a lot of flexiblility. |
Beta Was this translation helpful? Give feedback.
-
Change the way lists are displayed
Sorry, I dont know the terminology here, but when you press on a drop down list slot in the logic bricks in order to pick an item, the names of the items are displayed differently from how they are displayed elsewhere in blender - long names are cut off at their end, while in blender currently the names are cut off in the middle, and the ends are shown, which is much more useful when using long names to organize your objects in the scene.
Notice the difference between the drop down list name in blue and the one shown in the red box.
PS: Another request would be to add an object picker for the Message actuator, since it is used frequently and right now you need to be scrolling the names of the objects of the entire scene, instead of being able to manualy pick them as you would with the Edit object actuator.
Beta Was this translation helpful? Give feedback.
All reactions