Official Project Tiny 0.26 preview is available

I have been waiting for 3 months for you to add System.Net.
When will it be?

 

I don't think most of the code in System.Net could work in WebGL/WASM

 

Its too hot.Runing wasm or asmjs project in ios safair. That's why?

 

I need to use Tiny as a server.
Because the Unity build eats at least 90MB of RAM.
This is too much for the server of a particular game (session).
For each game on the server 90 MB...

1. I need to use NetCode.
2. And I also need to use a web server so that 1 server build can include multiple games (sessions), and for this I need System.Net.

 

I will also add that I studied the NetCode code, and made changes in two lines to add the ability for the server build to have a ClientWorld when the server is assembled as a headless one, so that this ClientWorld can communicate with the main server based on NetCode, designating itself as a GameSessionManager, and creating a game session on request from the main server.
Then in this case I can do without a web server. But it's too complicated, and I gave it up. I only spent a lot of time studying the NetCode source code)

 

Will the team be adding Unity.Transport support to TINY so we can make some kinds of connected game?
If so, any rough date?

 

Is Project Tiny 0.26 ready to eliminate the 16:9 limit and enable true automatic resizing to fit the browser window？

 

Its too hot.Runing wasm or asmjs project in ios safair. That's why?Android Is OK.

 

So in the future in Tiny I will be able to create an HTTP server and use NetCode?

 

1. Сan you find out about implementing a web server?
2. Answer about the NetCode. Will the NetCode server be in Tiny?

 

Networked games are an extremely important feature. Especially so for tiny so that it is possible to create a small executable where you can play with friends

 

have you planned to add skybox reflections support (or reflections in general)? i'm developing a simple web 3d model viewer, but metallic materials (obviously) are not metallic at all (and this forced me to use three.js)

 

Here Unity has mentioned "plans for a server" and "HTTP client side". Perhaps just Unity.Transport support as a simple starting basis? Might that be in the works?

 

I see that the Base Class Library supports System.Runtime.InteropServices and DllImport.
Does it also supports AOT and MonoPInvokeCallback?

Needs that to communicate with JS.

 

Will this be a regular DOTS package that will be usable in normal DOTS projects or will this be exclusive to project tiny?

Is there any rough ETA for performant webrequests at all?

I imagine the API to be something like just creating an entity with component data that describes the header and body of the request and getting back an entity with the results.

Which brings the question, how would json serialisation and deserialisation be handled in DOTS and project tiny? I see that newtonsoft is a dependency but that's all completely object oriented. Literally, it has object notation in the name...

 

To me, that's the most exciting news I've heard out of all developments under the DOTS umbrella. In my usecase, I make web requests to authenticate a user and retrieve JSON objects that describe mesh geometry and meta data associated to each mesh. The top of the JSON hierarchy is fairly constant but as you travel into the object structure there will be more and more variance in the data's schema.

This data could be mutated in any way including nesting additional arbitrary objects within the JSON object and posting that back up to the server.

BlobAssetReferences sound like they'd be a great fit for containing JSON data except for the fact that they are designed to be immutable (though I've found a sneaky way to get around this), they do not support key-value pair fields and there is currently no other alternative for accessing arbitrary object structures via ECS. Will this new DOTS compliant JSON API introduce an alternative to BlobAssetReferences or will it extend on the foundations BlobAssets have already laid out?

Also, are there any notable limitations of a DOTS compliant Web API and JSON API that you can foresee at this point being a challenge or are the core aspects of these ideas all reasonably achievable in DOTS?

 

this is a joke

 

What a constructive comment.

 

Hello nice to hear this awsome news, i need json or yml to get positions and rotations for the scene objects Positions. it will be all loaded from a server.

i want to ask if transparency will come to the materials, this would be pretty important for me

 

You can use bytes instead of JSON)
There is transparency in the materials.

 

thx for your awnser.
yeah i saw, need to activate in the URP renderer
is it Possibile to runtime load and show FBX files in Tiny? even with a Plugin