fuseeprojectteam / fusee Goto Github PK

In Fusee.Base.Imp.Android and Fusee.Base.Imp.Desktop the references for SharpFont and Freetype are all to debug libraries.

There are some little Bugs and things to be done in the physics system so we can integrate it in the next release.

With the latest JSIL update, we have to update our custom implementations.

This is how it looks like right now:

JSIL.MakeClass($jsilcore.TypeRef("System.Object"), "Fusee.Engine.Font", true, [], function($interfaceBuilder) {
    $ = $interfaceBuilder;

    $.Field({ Static: false, Public: true }, "CharInfo", $jsilcore.TypeRef("System.Array", [$fuseeCommon.TypeRef("Fusee.Engine.CharInfoStruct")]), null);

    // ...

    $.Method({ Static: false, Public: true }, ".ctor",
        new JSIL.MethodSignature(null, []),
        function _ctor() {
            // not implemented
        }
    );

    $.Method({ Static: false, Public: true }, "get_Width",
        new JSIL.MethodSignature($.Int32, []),
        function get_Width() {
            return this.Width;
        }
    );

    // ...

    $.ImplementInterfaces(
        $fuseeCommon.TypeRef("Fusee.Engine.IFont")
    );

    return function(newThisType) { $thisType = newThisType; };
});

This is how it should look like:

(function Font$Members () {
  var $, $thisType;

  var $T00 = function () {
    return ($T00 = JSIL.Memoize(System.Array.Of($asm01.Fusee.Engine.CharInfoStruct))) ();
  };

  // ...

  function Font__ctor () {
  }; 

  function Font_get_Width () {
    return this.Font$Width$value;
  }; 

  // ...

  JSIL.MakeType({
      BaseType: $asm05.TypeRef("System.Object"), 
      Name: "Fusee.Engine.Font", 
      IsPublic: true, 
      IsReferenceType: true, 
      MaximumConstructorArguments: 0, 
    }, function ($ib) {
    $ = $ib;

    $.Method({Static:false, Public:true }, ".ctor", 
      JSIL.MethodSignature.Void, 
      Font__ctor
    );

    $.Method({Static:false, Public:true , Virtual:true }, "get_Width", 
      JSIL.MethodSignature.Return($.Int32), 
      Font_get_Width
    );

    // ...

    $.Property({Static:false, Public:true , Virtual:true }, "CharInfo", $jsilcore.TypeRef("System.Array", [$asm01.TypeRef("Fusee.Engine.CharInfoStruct")]));

    // ...

    $.ImplementInterfaces(
      /* 0 */ $asm01.TypeRef("Fusee.Engine.IFont")
    );

    return function (newThisType) { $thisType = newThisType; }; 
  });

})();

We have to fix this asap!

On most machines VS-Code generates the FUSEE Application DLL into ${workspaceRoot}/bin/Debug/netstandard2.0/
On some machines VS-Code generates a subdir between Debug and Netstandard.
The "Debug in FUSEE Player" Debugger option relies on the "/bin/Debug/netstandard2.0/" sequence of subdirs.

Either find a way to remove the subdirectory names or find a way to keep VS-Code from generating additional subdirs.

• Fusee.Base.Common
• Fusee.Base.Core
• Fusee.Base.Imp.Android
• Fusee.Base.Imp.Desktop
• Fusee.Base.Imp.Web
• Fusee.Engine.Common
• Fusee.Engine.Core
• Fusee.Engine.Imp.Font.Desktop
• Fusee.Engine.Imp.Graphics.Android
• Fusee.Engine.Imp.Graphics.Desktop
• Fusee.Engine.Imp.Graphics.Web
• Fusee.Engine.Imp.Input.Desktop
• Fusee.Engine.Imp.Input.Web
• Fusee.Engine.Imp.Network.Desktop
• Fusee.Engine.Imp.Network.Web
• Fusee.Engine.Imp.Physics.Desktop
• Fusee.Engine.Imp.Sound.Desktop
• Fusee.Engine.Imp.Sound.Web
• Fusee.Engine.Imp.Video.Desktop
• Fusee.Engine.Imp.Video.Web
• Fusee.Engine.Player.Android
• Fusee.Engine.Player.Core
• Fusee.Engine.Player.Desktop
• Fusee.Engine.Player.Web
• Fusee.Jometri
• Fusee.Math.Core
• Fusee.Serialization
• Fusee.Xene
• Fusee.Xirkit
• fuseeCmdLine

• Create IImageData interface
• Implement ImagePixelFormat and ImagePixelChannel descriptive structs.
• Make current ImageData implement IImageData
• Enhance existing Blt implementation using the specified Src's ScanLine enumeration

Do some work

The Android build dies when trying to load assets via AssetStorage.Get<T>(Filename).
Digging deeper the difference is that ApkAssetProvider.CheckExist(string id) returns true in VS2017 and false in VS2019.

This is with VS2019 Preview 2.2

When running webbuild with Chrome the application crashes with:
WebGL2 context not found!

Solution:

1. Goto: chrome://flags/#enable-webgl-draft-extensions
2. Enable the draft extensions
3. Restart
4. Reload project - it should work now
5. WebGL Extensions can be disabled again from this point forward

• Example Bone Animation
• Example Bump Mapping

• Add RenderContext.SetShaderEffect(ShaderEffect se)
• Remove all RenderContext/GPU specific stuff from ShaderEffect internals
• Add Changed/Disposed event to ShaderEffect
• Add Lookup table to RenderContext to keep track of already allocated shaders for a given RenderContext
• Find a way to handle 1:n relationship between ShaderEffect and Shaders
• Move ShaderEffect.RenderMesh functionality to RenderContext.Render(Mesh m) and remove ShaderEffect.RenderMesh
• Find a more typed way for implementing ShaderEffect.SetEffectParam / GetEffectParam
• ADVANCED: inherit ShaderEffect from DynamicObject and make all declared parameters
  dynamic properties such that shader parameters can be set by myShaderEffect.MyCustomParam = xyz;
• Debug repeated RenderContextImp.CreateShader calls
• Avoid unnecessary OpenGL set uniform parameter calls
• Experiment: Try dynamic with nuget package in player.cs
• Compare value update: float4x4 compare
• Documentation
• BugFixes in Examples!

The Input feature for different controllers and gamepads has to be tested. For web and native code.
The corresponding example needs to be checked and (perhaps) cleaned.

Different GamePads have to be tested for native and browser:

• XBox360 Gamepad
• Ps3 Gamepad
• Keyboard & Mouse
• ...

There might be a problem with inverted axis in the web browser. This has to be corrected.

When attempting to build the Fusee.Engine project from the master branch, Fusee.Serialization will stop as soon as the PrecompileTool gets executed.

OS: macOS 10.13.4
Mono: 5.10.0.160
IDE: Rider 2018.1 181.4952.142

When the attached file is imported to blender and then exported to .fus, the geometry in Fusee is upside down even tho it looks correct in Blender.

This can be fixed in Blender by Apply Object Transformations

The Blender exporter should do this by itself to avoid confusing the user.

points_uniform_mesh_supertiny_uv2.zip

Merge the two branches and clean them.

• Implement 9-slicing
• Implement event system for various interactions e. g. OnMouseEnter, OnClick etc.

"Audio.Instance.LoadFile" without setting the streaming bool to true will crash the application when hitting Escape.

Example Code (test with own mp3s):

using Fusee.Engine;

namespace Examples.BeeTheGame
{
    public class BeeTheGame : RenderCanvas
    {
        private IAudioStream _ton_1;
        private IAudioStream _ton_2;
        private IAudioStream _ton_3;

        public override void Init()
        {
           _ton_1 = Audio.Instance.LoadFile("Assets/SOUND1.mp3");
//("Assets/schmotzer1.mp3", true)
// mit (mind. einem) true kein Absturz aber auch keine Überlappung der sounds möglich
            _ton_2 = Audio.Instance.LoadFile("Assets/SOUND2.mp3");
            _ton_3 = Audio.Instance.LoadFile("Assets/SOUND3.mp3");
        }

        public override void RenderAFrame()
        {
            if (Input.Instance.IsKeyDown(KeyCodes.Space))
            {
                _ton_1.Play();
            }
            if (Input.Instance.IsKeyDown(KeyCodes.W))
            {
                _ton_2.Play();
            }
            if (Input.Instance.IsKeyDown(KeyCodes.S))
            {
                _ton_3.Play();
            }
        }

        public static void Main()
        {
            var app = new BeeTheGame();
            app.Run();
        }
    }
}

The particle system has some minor known bugs. They have to be fixed before the release.

• It's not possible to change the properties of the particle system dynamicly on the fly. If you change a propertie with the getter/setter methods, you have to wait until new particles are generated to see the changes.
• Sometimes the particle system crashes after a longer time even if the number of the particles does not change. This is a FUSEE related problem.
• The workflow for using the particle system could be a bit more intuitive

Clean the example projects to have a minimum base of examples in the project only. Merge some of them and get rid of unnecessary ones.

Protobuf runs into a System.OverflowException if the geometry in a .fus file is too large.
Example code at https://github.com/FUSEEProjectTeam/Fusee-Bug-SerializationOverflow

• FontMap.cs: create Texture instead of ImageData.
• Test behaviour of different UI Texts with different font sizes, which are using the same Font instance.
• Make texture size in FontMap variable, according to pixel size of the used font.
• Set maximum size of the FontMaps' texture according to maxium size that current graphic cards can handle.
• Font scaling: "fontSize" only adjusts the texture resolution, not the scaling of the font mesh. Rename to "fontResolution".
• MipMap: Currently automated? The set font size is the maximum value.

• transformcomponent add order can mess up scale
• fusee root path is only set once in SetupMachineWide.bat
• textures ColorFormat is wrong in android build RGBA <> ARGB_8888
• blender path is hardcoded in fuseecmdline
• fusee path with whitespaces causes jsil exception - needs testing, try calling jsil with ""
• GetMaterial() doesnt work for Principled Shader materials.

When using "dotnet new fusee" in a directory with dashes (e.g. Fusee-Test), the resulting launch.json will contain "Fusee_Test.dll" in the args field for the Fusee Player. The dll will build to "Fusee-Test.dll".

As we were trying to implement a 2D-GUI element into our project we noticed, after getting a look at the background, that the loaded picture (png) was rendered behind all the 3D elements in our scene (with an ortographic camera).
All changes to the z-pos of the load function (new GUIImage) for the image were ignored and made no difference.
After adding a second picture to the GUI, the first one was rendered as before, but the second one with the same z-pos was rendered in front of everything.
Changing the order of the GUI.Add Functions as well as the z-pos led to some strange and unpredictable outcomes.

We're sorry that we can't provide a how-to for reproducing this issue, but we've got a backup of our code and if there are questions about it, let us know so we can help.

The current picking results don't seem to take rotations in the scene graph into account. The example at https://github.com/FUSEEProjectTeam/Fusee-Bug-RotationPicking shows a cube, build to a .fus, file that was rotated in Blender by (-90, -90, -90). When a surface is clicked/picked the camera should rotate to a view, centering the picked point on the face.

Picking results should not only be provided as local coordinates, but also in global coordinates or even in reference to another component in the scene graph hierarchy.

Picking and picking example is currently broken

Remove MeshComponent. Use new Mesh type instead and move to Fusee.Serialization, also inherit SceneComponent container. Remove MeshComponentMap from SceneRenderer.

Clean some of the many protobuf.dll's so we can have a minimum and maybe relocate them in the project directory.

There is a problem with the protobuf precompiler on mac osx - there is no precompiler for mac osx.

So the project should be excluded on mac osx or the precompiler for protobuf-net has to be added.

LFG needs some use cases and some more love to integrate it in the new release. Some things we want to integrate is a subdivision surface algorithm as well as some convenience functions. To be updated ...

A Fusee web build from a template crashes when using Linq (probably others things too). Linq is used in out picking implementation.
This also initialy happened when I switched the platform to netstandard2.0, the fix was excluding System.Linq in the dead code analysis of JSIL (18f4fb1).
This is happening again when building a template with fusee publish --platform Web.

How to reproduce:

• Create a new fuse template project dotnet new fusee
• Add some picking to it.
• fusee publish --platform Web

Test and validate current implementation of bone animation

The latest Visual Studio 2017 15.9.0 updated introduced .vsconfig files to help with installation of Visual Studio. See https://docs.microsoft.com/en-gb/visualstudio/releasenotes/vs2017-relnotes#install

Make ResourceManager.Get("some.fus") resolve referenced texture files into ImageData or Texture objects.

• Implemenmt SceneTranslator with dummy-component raw -> high-level translation

• Fix current implementation of bump mapping
• Feature: Bump mapping in tangent space

Fusee.Serialization uses a static path to the netstandard2.0 mscorlib.dll.
Either:

1. Update the precompiler so it can find netstandard and netcoreapp
2. Update the SerializationCompileSerializer build step to find the correct path and pass it to the precompiler.

Creating the documentation for updating the libs in fusee so everyone can do the updates in the future.

• Bone Animation
• Fix and clean Bone Example
• Bump Mapping

• Add features from Blt-Example
• test on all platforms

Sdl2 application quit
Sdl2GraphicsContext (handle: 196608) leaked, did you forget to call Dispose()?
[Warning] OpenTK.Platform.SDL2.Sdl2GraphicsContext:196608 leaked. Did you forget to call Dispose()?
GraphicsContext leaked, did you forget to call Dispose()?
NativeWindowBase leaked, did you forget to call Dispose()?
Sdl2NativeWindow leaked, did you forget to call Dispose()?
[Warning] {0} leaked, did you forget to call Dispose()?
OpenTK.Platform.SDL2.Sdl2JoystickDriver leaked, did you forget to call Dispose()?
Sdl2InputDriver leaked, did you forget to call Dispose()?
[OpenTK] OpenTK.Platform.SDL2.Sdl2Factory leaked with 2 live resources, did you forget to call Dispose()?
OpenTK.Platform.Factory leaked, did you forget to call Dispose()?

The Engine.sln solution file in the root of the develop branch cannot be opened in mono 3.0.x on ubuntu(debian based) linux due to the first line in the Engine.sln file:

"Microsoft Visual Studio Solution File, Format Version 12.00"

This cannot be read by mono. To make it temporarily work, it is possible to change it manually to:

"Microsoft Visual Studio Solution File, Format Version 11.00"

The file format 12.00 is just not supported under Mono 3.0x.
Mono Develop 4.2.2 (which is Xamarin Studio 4.2.2) is currently not available for linux machines in a prebuilt and stable state. Xamarin 4.2.2 can open the file just normal under Mac OSX 10.9.1 Mavericks.

Objects with rotations around the X-Axis appear reversed (with negative x-Axis value) when exportet to FUSEE.