Search the Community
Showing results for tags 'ue4'.
Found 4 results
Hello HTC Engineers and devs, We are considering developing for the Focus + with the Wave SDK and had some questions we were hoping to get some advice on! 1) Engine version. Our title is built with UE4.21.2 We don't plan to upgrade the engine in the near future. We are wondering if the WaveSDK for UE4.21.2 is still able to be used, or an UE4 engine update is required? 2) SceneCapture2D. We use the SceneCapture2D a lot with our title (on Oculus Quest) and we've seen this WaveSDK forum thread from around 3 months ago: https://forum.vive.com/topic/6552-can-not-use-scenecapture2d-with-multiview-and-multiviewdirect/ We are wondering if this is still a known issue or it's been fixed. We had a similar issue with the Oculus Quest SDK too but had a fix. 3) Performance. When testing out some free games from the store, and when just using the Focus+ dashboard / store environment with no other apps running, there seems to be a lot of performance issues - Low frame rate, juddering, etc. Does the WaveSDK have Fixed Foveated Rendering to improve performance? I can't see it in the docs, but did see it mentioned in the forums. For reference, the current OS firmware we are using is: 2.04.623.2 4) Platform features like Leaderboards and Achievements. I quickly searched through the SDK docs but couldn't find anything regarding this. Does the UE4 SDK support leaderboards and achievements? 5) Tracking. When moving the controllers around, the tracking does not appear close to 1.1. We've seen a thread on the forum about drawing a figure-8 pattern and we will attempt that today. We are wondering what the tracking latency is for the controllers when working correctly. Thanks for reading and we'd appreciate any thoughts on the above. @Cotta
Hello, Recently I`ve been trying to set up the UE4 SRWorks plugin and run an example project. I did everything according to the instruction. Hotkey functions are all working well except the scanning function. When I press the Z key UE4 immediately crashes. I get it that there is a problem that array index out of bounds exception but why? I did not alter any code or smth, just installed the plugin according to the instruction. Has anybody ever encountered a similar problem? @Dario @Daniel_Y
Hi, dear community. i can't packaging my project correctly when i check “for distribution” in my project settings. here is my dev environment: installed android sdk as normal (nothing wrongs here.) ndk: 16b win10 pro 1903 Unreal Engine 4.22.3 Wave_3.1.4_unreal sdk. jdk: jdk1.8.0_77 here is the description of my problem: I have successfully prepared the Android development environment according to the document description (I can guarantee that this part has no problems at all, because I can successfully package normal Android projects), but as long as I enable the wavevr plug-in in in the UE4 project and check "for distribution" in the packaging settings, I cannot package. The error comes from a library called "mockito". If I enable the wavevr plug-in and uncheck "for distribution", then I can package normally. I reproduced this problem in a blank project ( with wavesdk enabled), the sample project you provided, and our own project. steps to reproduces: 1. Install Android SDK, NDK, JDK 2. Create a blank blueprint project and fill in the path of SDK, NDK and JDK in Android SDK under project settings. 3. Fill in the relevant information in the extra settings for < Application > section under advancedapkpackaging 4. Create a blank map called NewMap and save it under content. 5. Copy the WVR folder to the engine path, and copy wavevr to plugins / wavevr under my project. At the same time, enable the wavesdk plug-in in UE4, and disable oculusvr and steamvr at the same time. 6. generate apk keystore and config it. 7. Check "for distribution" under packaging settings 8. Hit packaging. What i expected: The package should be successful and a signed APK should be generated What i Got: Conclusion: It seems that this kind of error cannot be solved on my own. I hope you can check this problem. I have provided a complete log and a project that can reproduce this bug. FullLog.txt Thanks.