I'm hitting a strange issue that I can't explain. I'm developing a VR app in Unity and I've recently added the OVRLipSync for mouth movements. It works fine on every other machine except for OSX devices (I only have one, so it might be specific to this device rather than the OS). Another thing is that it works in a whole new project but not in the project I'm currenly working on - If I create a whole new project, import the LipSync package and run the sample it all works fine.
In the project I'm working on however it crashes out both in the sample scene and my own implementation. I have imported the OVRLipSync package and run the sample and as soon as it runs, the editor crashes. I have obviously ensured the OVRLipSync.bundle has permission to run within System Preferences.
The log file states:
OvrLipSync Awake: Queried SampleRate: 44100 BufferSize: 512
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37)
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
UnityEngine.Logger:Log (UnityEngine.LogType,object)
UnityEngine.Debug:LogWarning (object)
OVRLipSync:Initialize () (at Assets/Oculus/LipSync/Scripts/OVRLipSync.cs:265)
OVRLipSync:Awake () (at Assets/Oculus/LipSync/Scripts/OVRLipSync.cs:217)
(Filename: Assets/Oculus/LipSync/Scripts/OVRLipSync.cs Line: 265)
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.dylib
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.so
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle
E1115 10:21:07.861620 399812096 init_intrinsics_check.cc:44] CPU feature avx2 is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU.
E1115 10:21:07.862260 399812096 init_intrinsics_check.cc:44] CPU feature fma is present on your machine, but the Caffe2 binary is not compiled with it. It means you may not get the full speed of your CPU.
Loaded scene 'Temp/__Backupscenes/0.backup'
Deserialize: 64.066 ms
Integration: 493.917 ms
Integration of assets: 0.970 ms
Thread Wait Time: -0.236 ms
Total Operation Time: 558.717 ms
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.dylib
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.so
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.dylib
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle.so
Fallback handler could not load library /Applications/Unity/Hub/Editor/2020.3.16f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Oculus/LipSync/Plugins/MacOSX/OVRLipSync.bundle
*** Aborted at 1668507668 (unix time) try "date -d #1668507668" if you are using GNU date ***
PC: # 0x193b3b4f3 (unknown)
*** SIGSEGV (#0x0) received by PID 2995 (TID 0x117d4a600) stack trace: ***
# 0x7ff8074c2dfd _sigtramp
Related
My DS1005 multi-board dSPACE system recently had its companion PC upgraded to MATLAB r2019b and ControlDesk 7.1. Since upgrading, I have been unable to get a Simulink model to compile, with the MATLAB diagnostic window issuing the following error:
LOADING APPLICATION "Debug_Local.sdf" ...
PLATFORM: ds1005
*** ERROR: Memory alignment error (double word alignment required).
Could not download real-time application: C:\Experiments\MATLAB Files\ENME303_DS1005\Debug_Local\debug_local.ppc.
An error occurred while loading the application.
DsErrorHandling: Panic! Format string 'The Clib Wrapper is not initialized.' for code 0x2711 starts with invalid character 'T'. Expecting '%'!
LOADING FAILED (1)
*** Stopped RTI build procedure for model: Debug_Local.
----------------------------------------------------------------------
Error:The call to rti1005_make_rtw_hook, during the after_make hook generated the following error:
*** Stopped RTI build procedure
The build process will terminate as a result.
Caused by:
*** Stopped RTI build procedure
Note that the model builds without error - it is when downloading to the DS1005 that the problem occurs. The Simulink model "Debug_Local" consists of a DS2001 A/D block, memory store with write, and that is all.
Prior to software upgrade, the multi-board system performed flawlessly, so the problem is likely a software configuration issue rather a hardware problem. I have read dSPACE FAQ 239, which describes a procedure for determining the cause of memory errors, but due to the fact that my Simulink model is the simplest possible, its suggestions do not seem relevant here.
Searching the web for help, there is mention of a memory alignment option in MATLAB, but only for a toolbox, rather than for the MATLAB core product.
I have a problem, When I have built the solution, a runtime error appears in one eye on a corner. Is imposible to read, but I got a log file that sais what its on the console (I can read only the corner and I think is the same) and we are tested in debug, release, master... and the error persist. In editor mode on Unity, the error dont appear. The experience is the same but I cant have this.
I dont find anything on their documentation, and this happens in 2019 (where im working right now) and 2018.
Im using MRTK 2.0 RC1 Refresh.
Im working with Lenovo Explorer with Motion Controllers.
Loading native plugins
Loading AudioPluginMsHRTF.dll
Module information:
Built with Compiler Ver '191627012'
Built from '2019.1/staging' branch
Version is '2019.1.0f2 (292b93d75a2c)'
Release build
Application type 'D3D'
OS 'Windows 10 (10.0.17763) 64bit'
PlayerConnection initialized from E:/UNITY_2019_PROJECTS/BUILD VISUAL STUDIO/build/bin/x64/Release/AppX/Data (debug = 0)
PlayerConnection initialized network socket : 0.0.0.0 55050
Multi-casting "[IP] 172.30.13.181 [Port] 55050 [Flags] 2 [Guid] 737340049 [EditorId] 0 [Version] 1048832 [Id] UWPPlayerX64(MyPC) [Debug] 0 [PackageName] MyProject_vvjrt7vn67k36" to [225.0.0.222:54997]...
Started listening to [0.0.0.0:55050]
PlayerConnection already initialized - listening to [0.0.0.0:55050]
Plugins: Failed to load 'WindowsMRXRSDK' because one or more of its dependencies could not be loaded.
(Filename: C:\buildslave\unity\build\Runtime/Misc/Plugins.cpp Line: 223)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1050 Ti (ID=0x1c82)
Vendor:
VRAM: 4018 MB
Initialize engine version: 2019.1.0f2 (292b93d75a2c)
Failed to find spatial stage root, falling back to stationary tracking space type!
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 591)
Created eye textures with a "texture array" layout. The "single-pass instancing" stereo mode will be used.
Windows Mixed Reality spatial locatability state changed to Activating.
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 374)
The referenced script (Unknown) on this Behaviour is missing!
(Filename: C:\buildslave\unity\build\Runtime/Scripting/ManagedReference/SerializableManagedRef.cpp Line: 197)
The referenced script on this Behaviour (Game Object '<null>') is missing!
(Filename: C:\buildslave\unity\build\Runtime/Mono/ManagedMonoBehaviourRef.cpp Line: 333)
A scripted object (probably Microsoft.MixedReality.Toolkit.Input.MixedRealityInputSimulationProfile?) has a different serialization layout when loading. (Read 76 bytes but expected 288 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
(Filename: C:\buildslave\unity\build\Runtime/Serialize/SerializedFile.cpp Line: 2012)
UnloadTime: 41,373700 ms
Windows Mixed Reality spatial locatability state changed to Inhibited.
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 374)
Setting up 3 worker threads for Enlighten.
Thread -> id: 36ac -> priority: 1
Thread -> id: 4944 -> priority: 1
Thread -> id: 5280 -> priority: 1
Windows Mixed Reality spatial locatability state changed to Active.
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 374)
Windows Mixed Reality spatial locatability state changed to Inhibited.
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 374)
Windows Mixed Reality spatial locatability state changed to Active.
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 374)
Trimming D3D resources.```
I'm using Unity 2017.3.03f free personal edition, I've an application in unity that works normally in desktop and android platforms. However, When it's built for WebGL release (unchecked "development build" option") it gives this error in browser during loading splash screen:
> An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was:
uncaught exception: abort(-1) at jsStackTrace (webgl-11B.asm.framework.unityweb:2:27460)
stackTrace (webgl-11B.asm.framework.unityweb:2:27631)
abort (webgl-11B.asm.framework.unityweb:4:33732)
_il2cpp_gc_disable (webgl-11B.asm.framework.unityweb:2:204426)
scripting_gc_disable() [vNc] (webgl-11B.asm.code.unityweb:10:1)
_main [eNc] (webgl-11B.asm.code.unityweb:10:1)
callMain (webgl-11B.asm.framework.unityweb:4:32097)
doRun (webgl-11B.asm.framework.unityweb:4:32800)
_String_Join_m2050845953 [run] (webgl-11B.asm.framework.unityweb:4:32986)
runCaller (webgl-11B.asm.framework.unityweb:4:31614)
removeRunDependency (webgl-11B.asm.framework.unityweb:2:34407)
processDataJob#file:.../Build/UnityLoader.js:1:17079
I've tried to enable the development option and apply the steps of this article:
https://community.gamedev.tv/t/webgl-debugging/54948
to enable debugging symbols and disable stripping code engine to see the errors in browser console. But the Development version works without error, but when I return to release build "unchecking the development option" again, the same error appears.
and the log of browser console contains the following message:
> IndexedDB is not available. Data will not persist in cache and PlayerPrefs will not be saved.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:124
unreachable code after return statement[Learn More]
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:4519
missing function: il2cpp_gc_disable
UnityLoader.js:1:8039
-1
UnityLoader.js:1:8002
-1
UnityLoader.js:1:8039
Use of the motion sensor is deprecated.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:54097
Use of the orientation sensor is deprecated.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:54097
uncaught exception: abort(-1) at jsStackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27460
stackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27631
abort#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:33732
_il2cpp_gc_disable#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:204426
vNc#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:10:1
eNc#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:10:1
callMain#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32097
doRun#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32800
run#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32986
runCaller#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:31614
removeRunDependency#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:34407
processDataJob.../UnityLoader.js:1:17079
If this abort() is unexpected, build with -s ASSERTIONS=1 which can give more information.
154
UnityLoader.js:1:8002
154
UnityLoader.js:1:8039
uncaught exception: abort(154) at jsStackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27460
stackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27631
abort#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:33732
Vxq#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:32:1
y7c#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:23:1
ynq#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:32:1
handlerFunc#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:57395
jsEventHandler#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:53935
why does this error happen? is it because of using unity free edition, or because the application reads some text file from Resources folder at loading?
thanks in advance.
tl;dr: flashed firmware to 0x00000000 instead of 0x08000000, am I lost?
Hello,
my device is based on a STM32F103CBTx which came with a proprietary firmware and had readout protection on.
I connect to it with a ST-Link v2 SWDIO and SWCLK connected to PA13 and PA14 and this command:
sudo openocd -f /usr/share/openocd/scripts/interface/stlink-v2.cfg -f /usr/share/openocd/scripts/target/stm32f1x.cfg
I don't remember how I removed flash protection, but it worked as the original firmware didn't work anymore. Then I created a simple hello world firmware which pulls up and down three gpios and flashed it. The gpios are pulled up and down in 700ms intervals.
After flashing, I can't connect with openocd anymore. I forgot to specify the offset, the manual says the offset defaults to 0 and as it worked, I suppose instead of the boot loader my shitty hello world is pulling up and down some random pins happily… Is this possible? All other threads I found say the boot loader is write protected.
This is the last contact I had:
> halt
halt
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x01000003 pc: 0xfffffffe msp: 0xffffffdc
> flash write_image erase fw.hex
flash write_image erase fw.hex
auto erase enabled
target halted due to breakpoint, current mode: Handler HardFault
xPSR: 0x61000003 pc: 0x2000003a msp: 0xffffffdc
wrote 4096 bytes from file fw.hex in 0.285697s (14.001 KiB/s)
> reset
reset
jtag status contains invalid mode value - communication failure
Polling target stm32f1x.cpu failed, trying to reexamine
Examination failed, GDB will be halted. Polling again in 100ms
Any directions highly appreciated.
Edit:
What I get now, also tried another st-link:
% sudo openocd -f /usr/share/openocd/scripts/interface/stlink-v2.cfg -f /usr/share/openocd/scripts/target/stm32f1x.cfg
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.244356
Error: init mode failed (unable to connect to the target)
in procedure 'init'
in procedure 'ocd_bouncer'
flashed firmware to 0x00000000 instead of 0x08000000, am I lost?
No, it doesn't matter at all, they are the same.
After reset, the MCU loads the word at address 0 in SP, and the next one at address 4 in PC. The BOOT0 and BOOT1 pins control which memory gets mapped to 0x00000000. Usually, BOOT0 is tied low, and flash memory at 0x08000000 gets mirrored at 0x00000000.
instead of the boot loader my shitty hello world is pulling up and down some random pins happily… Is this possible? All other threads I found say the boot loader is write protected.
The factory bootloader is indeed write protected, openocd can't overwrite it.
However, your application could have reconfigured the SWD pins, by writing a wrong value in GPIOA->CRH or AFIO->MAPR, thereby preventing openocd from working. It's the most common cause of this problem.
Fortunately, there is a way to recover.
Connect under Reset
If the reset pin of the controller is held low for a while when openocd is started, the application is prevented from starting, and messing up the GPIO configuration.
Openocd can do this automatically, when
It's told to do so, the line reset_config srst_only srst_nogate is present somewhere in the configuration script.
The MCU reset pin is connected to the debugger hardware, pin 15 on an official ST-Link/V2.
Or you can do it manually, by whatever means your board provides. If you are lucky, it has a reset button, if not, you must find a way to somehow ground the MCU reset pin.
Pull the reset pin low
Start openocd
Wait until the Info : Target voltage line appears. Maybe a second longer.
Release the reset pin.
It requires a bit of trial and error, you'll get better with practice.
Then you can flash your improved application, which carefully avoids reconfiguring the SWD pins.
I successfully launched an emulator, but after displaying vitual device in system the following errors are occuring:
Renderer error: failed to create/resize pbuffer!!
draw: Could not use program error=0x505
draw: Could not use program error=0x505
draw: Could not use program error=0x501
draw: Could not glDrawElements() error=0x505
Failed to alloc 16777216 bytes for ReadBuffer
Suddenly, loading of virtual device stops. What should I do now?
I had same errors from two days, This is how I solved this issue
downloaded the appropriate system image(64 / 86 system)
allocated less memory(in my case it was 700mb) in avd manager while creating new device(my system has 4gb ram)
restarted emulator