Search found 19 matches
- 28 Mar 2018, 11:49
- Forum: General Discussion
- Replies: 1
- Views: 1144
Noesis 2 start-up crashes on Android
Hey folks! We are currently expecting some random crashes on Android similar to the previously reported ones (The app crashes on startup on Android) but less frequently. We noticed this now because our app is in use annually at this time and is now in a beta phase. Additional infos: Unity 5.5/5.6 Af...
- 28 Mar 2018, 09:58
- Forum: General Discussion
- Replies: 5
- Views: 3511
Re: Crashes on some devices randomly at DoInit() of Noesis
EDIT: Moved to new topic since I cant change the state of this one (https://www.noesisengine.com/forums/viewtopic.php?f=3&t=1356). Hey folks! We are currently expecting some random crashes on Android similar to the previously reported ones (The app crashes on startup on Android) but less frequen...
- 19 May 2017, 14:37
- Forum: General Discussion
- Replies: 1
- Views: 1576
[Unity] StringFormat overwriting data from source
Hey, I have encountered a problem, which i could not solve. It might be due to a misconception, but here this is what we have experienced. We have a data source "campaign" with a Name attribute, which is already filled in (from parsing a local JSON file). In a TextBlock in XAML we want to ...
- 26 Apr 2017, 14:54
- Forum: General Discussion
- Replies: 6
- Views: 4262
Re: [Unity] TextureSource leads to black image on Android
Issue created (https://bugs.noesisengine.com/view.php?id=1062) if someone wants to track the progress.
- 25 Apr 2017, 08:30
- Forum: General Discussion
- Replies: 6
- Views: 4262
Re: [Unity] TextureSource leads to black image on Android
The texture works fine in Unity (and on the OpenGLES2 device), I tried the texture as Sprite as well as setting the texture in code:
Seems the error message I posted isn't directly related to this issue.
Code: Select all
Cube.GetComponent<Renderer>().material.mainTexture = tex;
Seems the error message I posted isn't directly related to this issue.
- 24 Apr 2017, 10:52
- Forum: General Discussion
- Replies: 5
- Views: 3206
Re: [Unity] OpenGLES2 rendering problem
Hi,
I created a bugtracker ticket : https://bugs.noesisengine.com/view.php?id=1060
It failed using the NoesisView on the Main Camera.
You're welcome! Pls get back to me if you need more information.
I created a bugtracker ticket : https://bugs.noesisengine.com/view.php?id=1060
It failed using the NoesisView on the Main Camera.
You're welcome! Pls get back to me if you need more information.
- 24 Apr 2017, 10:39
- Forum: General Discussion
- Replies: 6
- Views: 4262
Re: [Unity] TextureSource leads to black image on Android
Hi, I tested your sample which also leads to a black screen on our test device (Samsung Galaxy Tab 4 7.0 http://www.gsmarena.com/samsung_galaxy_tab_4_7_0-6251.php ). Further I got the following error from the Android log: 04-24 09:18:15.456: E/Unity(4941): (Filename: ./Runtime/GfxDevice/opengles/Gfx...
- 20 Apr 2017, 18:13
- Forum: General Discussion
- Replies: 6
- Views: 4262
[Unity] TextureSource leads to black image on Android
Hi, the following setup leads to a problem when setting a texture (video) as Image.Source programmatically img.Source = new TextureSource(tex); : Unity 5.6.0p1 Noesis 2 Android (Problem appears when deployed to an Android device) An Image becomes black when setting a Texture as Image.Source on Andro...
- 18 Apr 2017, 16:43
- Forum: General Discussion
- Replies: 5
- Views: 3206
[Unity] OpenGLES2 rendering problem
Hey, we upgraded to Unity 5.6 and NoesisGUI2 for our latest project. Everything works fine so far except a rendering issue on OpenGLES2 devices (Android). While a solid color rectangle is rendered fine, using an linear gradient brush to fill a rectangle leads to unexpected results (pls see https://w...
- 03 Nov 2016, 15:06
- Forum: General Discussion
- Replies: 3
- Views: 2310
Re: [UNITY] Android x86 runtime error
Thx for your quick response!
It seems that we didn't import the Android x86 runtime. Re-importing solved the issue!
It seems that we didn't import the Android x86 runtime. Re-importing solved the issue!