Forums | NoesisGUI

Hi I've been able to build for windows on my mac using the steps I was give in this thread. No problems. Life was great. I don't know what is making the difference, but suddenly the Windows build of my game crashes when loading the main scene. The only thing that I can think of that may have affected the build is that I added some Unity GUI elements to the scene. However, i have since removed all unity gui elements to see if that would make a difference but it didn't.

To be clear the game loads. My initial scene loads-- which doesn't include any noesisgui elements, but the main scene in the game, which does have noesis elements, crashes.

The mac build of my game is working just fine, its just the windows build that crashes.

I'm using the latest Noesis version on the Unity store--I just updated it again today in hopes that maybe cleaning out everything would fix it, but to no avail. I'm on Unity 4.6.3. the build is Windows x86 and is built for Dx9 using the noesis-->Settings-->build button.

Here's the Dump. Below is crash readout. Any ideas would be appreciated. Thank you for looking at this.




{{{
[DX9] Resource ID for

• 'Drawing/VGL/vglMask.shader' not found

}}}
{{{
[ 0] [0x1DB334BA] Noesis.dll!Noesis::Core::InvokeErrorHandler + 0x6a bytes
[ 1] [0x1DB5EB29] Noesis.dll!Noesis::Gui::Visual::GetRenderer + 0x1a9 bytes
[ 2] [0x1DE76B56] Noesis.dll!Noesis::Gui::Animation<short>::AddReference + 0x206 bytes
[ 3] [0x1DE8F36B] Noesis.dll!NsShutdownPackages + 0x27b bytes
[ 4] [0x1DB43B25] Noesis.dll!Noesis::Core::TypeClass::GetClassType + 0x65 bytes
[ 5] [0x1DB327F3] Noesis.dll!Noesis::Core::Reflection::Cast + 0x33 bytes
[ 6] [0x1DB3868E] Noesis.dll!NsGetKernel + 0x22be bytes
[ 7] [0x1DB37602] Noesis.dll!NsGetKernel + 0x1232 bytes
[ 8] [0x1DB375B5] Noesis.dll!NsGetKernel + 0x11e5 bytes
[ 9] [0x1DB37B48] Noesis.dll!NsGetKernel + 0x1778 bytes
[10] [0x1DB36B8A] Noesis.dll!NsGetKernel + 0x7ba bytes
[11] [0x1DE03FF9] Noesis.dll!Noesis_Init + 0x1c9 bytes
[12] [0x101108CE] mono.dll!mono_gc_get_generation + 0x78a8 bytes
[13] [0x10001D44] mono.dll!g_free + 0x316 bytes
}}}

Hi,

In NoesisGUI 1.1, our package comes with some prebuilt resources that can't be deleted when a standalone is generated. They can be found under:
- StreamingAssets/NoesisGUI/Data/$PLATFORM/Drawing/VGL
- StreamingAssets/NoesisGUI/Data/$PLATFORM/Gui/Core

Apart from these, all xaml and fonts in your Unity project are also processed and runtime resources are generated under:
- StreamingAssets/NoesisGUI/Data/$PLATFORM/Unity/Unity

You must include all these files in your standalone because these are our runtime resources.
Is it possible you deleted these folders unintentionally?

Thank you for the quick response.

You must include all these files in your standalone because these are our runtime resources.
Is it possible you deleted these folders unintentionally?

All of those files and folders are there. None of them were deleted.

After talking about it today we decided--perhaps unwisely-- that it might be worth updating to noesis 1.2 to see if that would fix the issue. However, we are having issues after simply importing the package into a brand new project. This is in in Unity 5:

Multiple plugins with the same name 'noesis' (found at 'Assets/Editor/NoesisGUI/BuildTool/Noesis.bundle' and 'Assets/Plugins/Noesis.bundle'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor.

We've tried deleting one Noesis.Bundle or the other to see if one of these bundles was redundant, but apparently both are needed because Unity throws more errors if any are deleted. We also tried renaming, but to know avail. Why is this happening, and is there a work around to this?

Thank you for your help

All of those files and folders are there. None of them were deleted.

It's strange then...
Could you please create a ticket in our bugtracker and attach a standalone where we can reproduce the error. This way we can debug what is happening.

After talking about it today we decided--perhaps unwisely-- that it might be worth updating to noesis 1.2 to see if that would fix the issue.

Upgrading to 1.2 version will probably require some modifications to your code, because we changed our API to be more WPF-like. But there are also many optimizations you can benefit from.

However, we are having issues after simply importing the package into a brand new project.
We've tried deleting one Noesis.Bundle or the other to see if one of these bundles was redundant, but apparently both are needed because Unity throws more errors if any are deleted. We also tried renaming, but to know avail. Why is this happening, and is there a work around to this?

Yes, the package is not Unity5 100% compatible yet, and you need to adjust some things. First of all, NoesisGUI only works with Unity 5 32-bit Editor. And about the library conflict, better take a look at this post:
viewtopic.php?f=3&t=595&start=30#p3558

We are working to provide full compatibility with Unity 5 (64 bit Editor included) in the following weeks.