golgepapaz
Topic Author
Posts: 43
Joined: 01 Aug 2013, 01:59

Trial version of Neosis

01 Aug 2013, 11:33

hola;
I am evaluating the trial version of NeosisGUI for our project. When I try to add simple xaml file
of my own, Neosis complains about not finding it with the message;
Exception: [DX9] Resource Assets/silfolder/sil.xaml not found
Noesis.Error.Check () (at Assets/Plugins/NoesisGUI/Scripts/Core/NoesisError.cs:48)
Noesis.Kernel.Noesis_LoadXAML (System.IntPtr& root, System.String xamlFile) (at Assets/Plugins/NoesisGUI/Scripts/Core/NoesisKernelImports.cs:24)
Is this the limitation of the trial version or am I required to do some other things other than dropping the
file to the GUIPanel script?

Also on an unrelated note,the performance is horrible when working on our workstations with quadro FX3800 cards. FPS of primitives sample clocks around 3, The controlGallery sample is very sluggish during switching animations etc. Although it runs fine on conventional GPUs (geforce gtx560m).

This stuff is good.Keep up the good work.
 
User avatar
sfernandez
Site Admin
Posts: 1912
Joined: 22 Dec 2011, 19:20

Re: Trial version of Neosis

01 Aug 2013, 13:18

Could you please open our settings window under 'Component -> NoesisGUI -> Settings' menu option, and check that DX9 platform is selected, it should be set by default for Windows.

We need that .xaml and .font files are processed for the corresponding platform before we can use them.
 
User avatar
jsantos
Site Admin
Posts: 2904
Joined: 20 Jan 2012, 17:18
Contact:

Re: Trial version of Neosis

01 Aug 2013, 13:35

Also on an unrelated note,the performance is horrible when working on our workstations with quadro FX3800 cards. FPS of primitives sample clocks around 3, The controlGallery sample is very sluggish during switching animations etc. Although it runs fine on conventional GPUs (geforce gtx560m).
Could you do the same test in the XamlPlayer and check with the following variants:
  • Test the different MSAA methods and see how the performance change.
  • Check also the GL renderer and tell us the performance. To activate the GL renderer open XamlPlayer.ini (it is autogenerated the first time you launch it) and set
[Render.RenderSystem]
Render = "GL"

[Gui.Application]
ShowStats = true
 
ToddS
Posts: 14
Joined: 24 Jul 2013, 03:49

Re: Trial version of Neosis

01 Aug 2013, 23:47

I assume that you're using Unity based on the paths provided in your error message. I think I had gotten a similar error message about the xaml file not being found and it was because I had added it to the assets folder outside of Unity and tried to build it that way. The problem was resolved when I removed the file from the Unity project, and then used Windows Explorer to drag/drop a copy of it from another folder into the Unity assets window, so it may be related to how you added the xaml file to the project.

I'm just going from memory here but I think there's a build file that NeosisGUI needs for processing the xaml file, and it doesn't get generated if you add the xaml file to the assets folder outside of Unity.

Todd
 
User avatar
jsantos
Site Admin
Posts: 2904
Joined: 20 Jan 2012, 17:18
Contact:

Re: Trial version of Neosis

02 Aug 2013, 00:34

Yes, exactly. For each .xaml in the Unity project we need a .xaml.make that tracks the resource. That make file is automatically generated by our Unity plugin. In theory if you create the .xaml using the Windows explorer, the next time you switch to Unity, it is created... but there could be something wrong in our part (or unity not saying us that there is a new file in the project).

Let us investigate this issue, although any help that allows us to reproduce it is welcome.
 
golgepapaz
Topic Author
Posts: 43
Joined: 01 Aug 2013, 01:59

Re: Trial version of Neosis

02 Aug 2013, 11:30

Thanks for the answers, the problem is solved by manually building from the settings menu when I add a new
.xaml file. In my case, since I've written the file in visual studio there were elements not recognized by your builder/compiler.However, you only get the error or warning messages in the unity console if you manually build from the settings. Otherwise it silently fails with the aforementioned message in my first post.

Also some errors crashes/freezes the unity itself. I am guessing some native exceptions are not handled.

@jsantos
I only have the unity package so It will have to wait until we buy the engine.
 
User avatar
jsantos
Site Admin
Posts: 2904
Joined: 20 Jan 2012, 17:18
Contact:

Re: Trial version of Neosis

02 Aug 2013, 12:38

Thanks for the answers, the problem is solved by manually building from the settings menu when I add a new
.xaml file. In my case, since I've written the file in visual studio there were elements not recognized by your builder/compiler.However, you only get the error or warning messages in the unity console if you manually build from the settings. Otherwise it silently fails with the aforementioned message in my first post.
I did a very fast test. Opened one of my projects in Unity, created a file named DragList.xaml with the following content:
<Grid
  xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
  xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
  </Buuton></Button>
</Grid>
And when saving and returning to Unity, a .make file next to the xam is generated and the following error is shown in the Unity Console:
[GL] Assets/DragList.xaml
Parsing (@4,4)
Tag mismatch
UnityEngine.Debug:LogError(Object)
Noesis.BuildToolKernel:OnLog(Int32, String) (at Assets/Editor/NoesisGUI/NoesisBuildToolKernel.cs:146)
System.Object:wrapper_native_0x25150756()
Noesis.BuildToolKernel:Build() (at Assets/Editor/NoesisGUI/NoesisBuildToolKernel.cs:122)
NoesisPostProcessor:Build(String, Boolean, Boolean) (at Assets/Editor/NoesisGUI/NoesisPostProcessor.cs:206)
NoesisPostProcessor:OnPostprocessAllAssets(String[], String[], String[], String[]) (at Assets/Editor/NoesisGUI/NoesisPostProcessor.cs:173)
UnityEditor.AssetPostprocessingInternal:PostprocessAllAssets(String[], String[], String[], String[], String[])
Can you reproduce this in your machine?
Also some errors crashes/freezes the unity itself. I am guessing some native exceptions are not handled.
We are improving the stability in each version. Today we are releasing v1.0.1. It would be great if you could post here all the .xaml that crash unity.

Thanks!
 
golgepapaz
Topic Author
Posts: 43
Joined: 01 Aug 2013, 01:59

Re: Trial version of Neosis

02 Aug 2013, 12:54

Can you reproduce this in your machine?
Thanks!
Yep. I've probably not noticed the errors the first time and I have clear on play selected.
So feel free to ignore me..
 
golgepapaz
Topic Author
Posts: 43
Joined: 01 Aug 2013, 01:59

Re: Trial version of Neosis

16 Aug 2013, 16:29

Could you do the same test in the XamlPlayer and check with the following variants:
  • Test the different MSAA methods and see how the performance change.
  • Check also the GL renderer and tell us the performance. To activate the GL renderer open XamlPlayer.ini (it is autogenerated the first time you launch it) and set
[Render.RenderSystem]
Render = "GL"

[Gui.Application]
ShowStats = true
Not exactly sure if this the right place but we've bought two licenses from asset store. how do I download the sdk?
Invoice numbers are 301272934 and 301272935.could you validate this account ?
 
User avatar
jsantos
Site Admin
Posts: 2904
Joined: 20 Jan 2012, 17:18
Contact:

Re: Trial version of Neosis

18 Aug 2013, 19:23

I have sent you en email.

Who is online

Users browsing this forum: Google [Bot] and 0 guests