a node or component similar to websocket but for udp packets

Not sure if this is a good idea but since this will be for features people want and to essential not use mods or since using this with NML is kinda bad porting some mods to this might be handy

• Semi automatic setup for shadow and collider meshes

  • set main mesh to no shadow / collison
  • creates necessary components and links them to corresponding objects

• Based on naming conventions

  • shadowmesh, shadow, lightblock, etc

• Neos issues:

  • no open ones

Create nodes for various physical calculations, such as friction, drag, refraction, etc.

• Setup the lod component based on configured presets

  • percent limits per lod level

• Based on name schemes, for example:
  - objectname_LOD0, objectname_LOD1, etc

• Neos issues:

  • Neos-Metaverse/NeosPublic#173
  • more advanced version: Neos-Metaverse/NeosPublic#174

• Reverb and echo for spatial audio sources

  • currently both effects are only "globally" applied to broadcast
  • this leads to issues with for example players user broadcast "in a cave" setup
  • Could be build around the steam audio features implementation

• Neos issues:

• Neos-Metaverse/NeosPublic#2693

Currently there is only split in pieces by materials but having it be able to be split in all the seperate pieces and join them again in groups or something like the in blender option would be nice i thought of this idea when j saw that a skinned mesh with the cloth physics becomes all the seperate pieces when you collide it with cloth collider

Get JSON data from a specific integer (Like Multiplex) and amount of objects / data

{
    {   0
        "TestData":"123456"
    },
    {   1
        "TestData":"321654"
    },
    {   2
        "TestData":"321654"
    }
}

And amount would count to 3.

• raycast / collision filtering

  • bepu seems to support filtering of collision / raycast events
  • this could be helpful if you want to only "hit" certain objects

• Neos issues:

  • Neos-Metaverse/NeosPublic#3123
  • Neos-Metaverse/NeosPublic#2058
  • Neos-Metaverse/NeosPublic#403

Have the Bepu physics engine run on its own tick rate

Provide UIBuilder functionality using LogiX nodes.

• New Cloth collision types such as box, mesh, plane, inverted colliders(Don't know if this would be mesh or not)

• • Temp solution is have a Capsule/Sphere collider be really large in the world

• Have the Add PinningCoefficients button index by from the prior items VertexIndex

• • Prevents RSI

• Have the ability to grab all colliders from a referenced slot and if it is null grab all from root

• • Prevents RSI

• Have a list stored on the Host's client for when a Cloth collision is attached and have it added via "OnAttach" or "OnAwake"(Not to sure)

• • Theoretically better but not sure

Neos-Metaverse/NeosPublic#60

Yes, I know these listings are getting absurd, but I'd like to actually start discussing these kinds of things sooner rather than later. Or at least considering alternatives to solutions that are commonly proposed.

In a nutshell, some rudimentary way to compile C# to LogiX. This would involve analysis of the C# code, mapping it to some sort of equivalent LogiX representation, optimizing the data flow a bit, and grouping/arranging the nodes so that they are not a jumbled mess at the end of the process. The hardest part will be figuring out the mapping.

I don't think C# as the source language makes a lot of sense here. We're dealing with two separate programming paradigms here, and the object-oriented functionality of C# doesn't lay out well in a flatter, functional context. An option is to define a new scripting language (say, LogiXScript) and use that as a textual, high-level way to define a LogiX graph.

Two Add Component nodes.

Left (Presumably the wrong node):

Right:

Allow specifying value or reference fields to target for a component. Allow reading/writing fields.

loading vrm model files and possibly auto configuring to an avatar.
perhaps even loading from web resource like hub.vroid.com

• Material properties

  • A collection of properties that define how an object reflects, absorbs, and transmits sound.
  • https://valvesoftware.github.io/steam-audio/doc/unity/material.html
  • interesting for combining with physical materials of bepu physics

• Neos issues:

  • no open ones

(Based off of this comment on issue #57)

Ability to use + & - nodes to group together User References to input into thing like Ignore User on certain nodes.

However on second though there might need to be some redoing of some of the nodes now that I think about it to make this compatible.

this has been a problem that has been plaguing NEOS since Logix was created I don't think I'm the only one that finds duplicate interfaces really annoying and irritating

• bepu physics allows to define material properties and trigger collision events based on that

• it should be possible to combine this with the Steam Audio material properties to get dynamic interactions based on that

• for example:

  • trigger different sounds based on both materials

• Neos issues:

  • no open ones

So basically the find slot by tag but then instead of only 1 finding all slots by tag if there is multiple so it collects them and then when collected all you can do something with them

• Froox did some in-depth changes to the way ray casts from the bepu physics work

  • he mentioned forcing a synced update, instead of the original, separate thread approach

• They are way more heavy on performance than they need to be

  • if you watch closely at the numbers in the provided unity demo scenes (or the video show casing raycasts), we should have way more head room there

• We need to take a look at the "intended way" of using them

• Neos issues:

  • no open ones, only a comment of Froox at the end of the mmc traffic system show case

• cloth physics

  • Froox said to not use the bepu "native" cloth simulation
    • seems to be based around "one sphere collider per vertex", which can get expensive really fast
  • may needs another approach with similar results

• Neos issues:

  • Neos-Metaverse/NeosPublic#2853

• the current particle system in neos is pretty limited

  • "custom" implementation by froox
  • some features are there, but hidden / not accessable by normal means

• try to implement most of the features from the native unity particle system

• Neos issues:

  • Neos-Metaverse/NeosPublic#2654
  • Neos-Metaverse/NeosPublic#1608
  • Neos-Metaverse/NeosPublic#786

Create & add to arrays. Aswell as modify obviously

Allow the creation of arbitrarily-typed reference registers.

So it is one less compatibility to worry about because then if you use mods with Neos+ you only need Neos+ and no need to spoof compatibility hash when using Neos+ with mods since then neos+ would incl the thing to load mods and then it would be just Neos+ incl NML and then show up as using Neos+.DLL since then you only need Neos+ but I'm not talking about it combining both permanently but only adding it to here so it is incl and ofc you then don't spoof the hash since Neos+ being a seperate hash is good so you don't accidentally join people that don't have it but at the same time can use all the mods that you use on NML so then i would launch Neos+ if i wanted to play Neos+ with mods and just launch NML if i play regular Neos with mods so Neos+ would still show up but as only requirement as needing the Neos+ to join

like the find child by name but for components you put in the string which is the name and then if it finds the component on specific slot you plugged it into

Currently, the JSON tools only provide parsing options. Being able to create and export JSON objects would be useful.

• Distance based network lod

  • Froox had a concept idea about changing the data update rate, based around the distance between users

• Neos issues:

  • similar: https://github.com/Neos-Metaverse/NeosPublic/projects/13#card-61308266

I would like BEPUv2 rigid bodies to be integrated into Neos Plus so that I can create buildings that can be destroyed along with a lot of other things

Currently, the Users>User Root folder is missing several potentially useful outputs, such as Left/Right Foot Position/Rotation. There are also missing nodes for setting certain values. Overall, the folder is quite inconsistent and needs an overhaul.

• extend the existing light wizard with new features
• set brightness by value instead of the current multiplying implementation
• get lights based on filters
  • type, color, etc
• set max distance based on raycast measurement to surfaces
  • spot: take the z axis direction
  • point: select able rules, for example:
    • sphere like measurements and taking the averge or something like that
• light setup templates
  • library of user created templates for easy reuse
  • can already be build with limited features inside of neos itself
• Neos Issues
  • Neos-Metaverse/NeosPublic#1996
  • Neos-Metaverse/NeosPublic#1995
  • Neos-Metaverse/NeosPublic#1994

Neos-Metaverse/NeosPublic#221

• rigged body support

  • high demand by a lot of users
  • how to simulate and sync between clients?

• Neos Issues:

  • Neos-Metaverse/NeosPublic#22

This would be nice since I think it will be worth it since recording 360 video currently can only be done via an alt account running on a seperate Neos instance that launches 360 mode but having it in-game on main yeah it might be more performance on the gpu but running 2 Neos instances is even more laggy than just 1 with 360 streaming camera so this feature added to the streaming camera would be Really good

• Trying to add more, if not all features of steam audio into neos

• The unity plugin could be a good start, since it contains components for all usable features

  • https://valvesoftware.github.io/steam-audio/doc/unity/index.html
  • example: https://youtu.be/2H_hlHaBOVA

• Neos issues:

  • Neos-Metaverse/NeosPublic#2693
  • Neos-Metaverse/NeosPublic#644

Simple FFT implementation using C# directly or a C# wrapper around a C library. Would need to investigate a performant means of implementing this. I'm debating how the data should be pipelined. Perhaps the component receives a reference to an audio clip player and a window size and outputs the values through a ValueStream, which then can be used in a custom multi-driver that can drive various fields. Or perhaps there would be an option to specify a frequency to sample, returning the corresponding amplitude.

• Physical materials

  • implement similar features as unreal engine
    • https://docs.unrealengine.com/5.0/en-US/physical-materials-in-unreal-engine/
  • bepu already has custom triggers based on materials

• Neos issues:

  • no open ones

Fix fbt so setting to lock the avatar head to the headset position instead of locking the hip

• apply transform (scale, rotation, position), similar to blender feature

• for the position you would change the origin point of the mesh

• Neos issues:

  • no open ones

• Ragdolls?

  • helios does it, would be "funny"
  • should be a toggle to avoid discomfort
  • optin if used for games
    • knock out -> keep player view add headset and instead of following the body

• Neos issues:

  • no open ones

asset management in terms load priority to set slots and there components to be loaded first.
example: spawn area or floors

Currently, most discrete-calculus-type operations have to be performed manually. Having nodes to integrate and differentiate, as well as perform certain vector calculus operations (divergence, curl, etc.) could be worthwhile. Usage of such nodes would mostly consist of supplying one or more inputs to vary and zero or more setting inputs for controlling the integration interval, among other uses.

Like Nearest User Head, but gets the User ref instead.

Just an idea, i'm entirely not sure if this is possible, please tell me if this is unrealistic.

Some sort of UI when creating an avatar kind of like Unity's humanoid rig assignment to assign certain bones manually so you don't need to rely on the Heuristics all the time (though you should name the bones right.). This could allow for re-initialization of the avatar rig in case you have your finger bones or something named wrong, and you can manually assign and fix it, not having to go back into blender and rename the bones, then re make the entire avatar.

A nearest user node so we dont have to use Get Nearest User Head.

Add headers to HTTP requests as we can't do any sort of authorization with API's such as GitHub

https://github.com/Faolan-Rad/FaoLogiX that would be really nice to have in here

Currently, Random only supports a handful of types, such as Bool, Int, and Float. Only Float has support for vector types. Let's add more types and vector types.