I have recently ported our application from Qt5.5 to Qt5.12.1. On i5 processor Windows 10 the application runs fine. However on i3 Windows 10 Pc's we get a nothing but a black screen. The application runs fine on i3 Windows 8 though.
On further digging, we found out that the issue occurs only on devices where OpenGL version is 3.x and it works when the OpenGL version is 4.0+. That's why it worked in i3 windows8 which has 4.0 version of OpenGL.
For Qt5.5 it works, but if we port to even Qt5.6 it does not work. We cannot find anything on release notes or known bugs from Qt. We are using OpenGLfunctions and QOpenGlWindow.
Information from the logs of Qt5.5 build:
glVersion 3.1.0 - Build 9.17.10.4459
Information from the logs of Qt5.6 and 5.12.1 builds in the same machine and same environment:
glVersion - OpenGL ES 2.0 (ANGLE 2.1.0.57ea533f79a7)
I would like to know whether I am missing something that I should do while porting Qt versions? or is it a bug in Qt?
How can I force Qt to use available OpenGL version instead of using ANGLE?
I would also like to know if we can downgrade OpenGL version of the windows 10 to re-create it easily on other devices as well for testing purposes.
Thank You.
Related
I have taken the "default game" (tables and chairs) of Unreal Engine 4.26, and packaged it for the Hololens emulator using these instructions.
I can launch the latest Hololens emulator (10.0.19041.1136) and install the Unreal application, and an icon shows up for it in the apps panel. But when I launch the app, the entire screen is black. When packaging the application for Windows (64 bit), the application works just fine.
What could be the issue? Older versions of Unreal Engine work fine, in particular I have verified that Unreal Engine version 4.25 works with the emulator.
Other perhaps relevant info: Intel Core i7-5960X, Windows 10 version 1909 build 18363.1440, NVIDIA GeForce RTX 2080 Ti, Version 456.71.
I have also used the Unreal 4.26-chaos engine, completely fresh. I choose a blank project from the Games category, C++, Scalable 2D or 3D, raytracing disabled, mobile/tablet with starter content. Then add the Microsoft Windows Mixed reality plugin and the Hololens plugin. In settings I get a signing certificate and define a project name, using Windows SDK version 10.0.18362. Again, no joy. The same thing, just as a Blueprint, not a C++ project, also does not work.
Also checked Hololens emulator version 10.0.19041.1117. No joy.
We followed all the steps exactly per docs including the “run in VR mode setting” in packaging and reproduced this issue today.
So, we are going to recommend to you to file a defect over with UE 4.26 via Unreal Engine Support | Get Help and Customer Service for UE - Unreal Engine. Besides, you can also open a support case via http://aka.ms/hololenssupport for free to discuss further too on anything we can offer for HoloLens 2 emulator/device:
The issue in the Epic's article. You should enable the "start in VR" option in Project > Description > Settings as from
https://learn.microsoft.com/en-gb/windows/mixed-reality/develop/unreal/tutorials/unreal-uxt-ch6
It was added in 4.26.
And we don't support Unreal 4.26-chaos yet. Please take simple 4.26.
I've browsed through many topic and answers related to the emulator crashing issue. Yet, I still have no clue how to resolve this issue.
My setup:
Windows 10 x64 laptop - 16GB RAM - Intel Core i7-6820HQ CPU # 2.7Ghz
Android Studio 2.3.3
Java JDK jdk-8u141-windows-x64
HAXM installed and activated
When I open Android Studio, I can start the emulator without any issues.
(see picture here)
But when I try the same from the commandline, the emulator does not startup properly and stops. (see picture here)
I've tried:
HAXM 6.0.6 and HAMX 6.1.3
Graphics: Software GLES 2.0 (instead of auto)
RAM: lowered to 512 (instead of the default 1536) as mentioned in many posts
Try a emulator with lower resulution (like Galaxy S 800x600) as also mentioned in many posts
Use arm image to trigger arm emulator
Add MB behind certain values in the ini file
Set the width/height value to 0 in the ini file
Turn off the camera (front and back) emulation
Disable multi-core CPU (since it mentioned behind it that it's experimantal)
I tried the emulator in the tools folder and the emulator folder
What am I doing wrong here?
What else can I try?
Did I forget a combination of the above mentioned items?
My end goal:
I want to make this emulator part of my CI cycle and for that I need to run a command line (or powershell) script on a Hyper-V machine (in Azure), to start this emulator, so I can hook it up to my selenium-grid (via Appium).
I had the same problem, I fix it by updating my windows (windows 10) to the latest version (windows 10 version 1903 build 18362) and take the optional update (KB4512508)
in the windows update setting..
I'm using:
- Windows 10 Enterprise.
- AMD A10-4600M APU withe Radeon HD graphics.
- ram 512.
Try this solution it worked for me.
I've been building a game in Unity using the Affectiva Unity SDK, and I can test the game out within Unity fine - the camera turns on, the SDK is called, and I get the response I was expecting.
Yet when I go to build the project, it claims it builds successfully and the camera is activated when the scene starts.. but I get no responses from the SDK. No errors or anything..
Do I need to package this up specially or something?
I suspect the issue is that you are building a 32-bit app on OS X. Is that correct? If it is, can you instead create a universal build or a 64-bit build? The Unity plugin currently only supports the following build options:
Windows 64-bit
Windows 32-bit
OS X Universal
OS X 64-bit (x86_64)
For some odd reason Unity defaults OS X builds to 32-bit. There is documentation about the build requirements on Affectiva's developer portal at the bottom of the page.
I have a laptop with i5 configuration and I have a PC with Intel Q33 motherboard and core2Deo. In my i5 its work fine but in Q33 first give me OpenGL error but I upgraded the graphic driver and the problem solved. But in my PC when I start a genymotion device it start with white screen and dost allow any thing to touch...
I have done following solution
upgrade my Graphic Driver
Reinstall VBox of oracle
Reinstall Genymostion and download devices
so it no issue with installation of the genymostion but still i gatting white screen ...
Upgrade your OpenGL Version to 2.0 or higher.
Please Check Requirement of Genymotion and check your system configuration.
In VMbox the android virtual machine is working. and on geymotion having the same above issue.
I have update my video card too .. using win 7
Now I get to know that my chipshet have no updation for OpenGl.
So, It's not going to work for me.
If you want to check your Opengl version then download the below link:-
http://ononesoft.cachefly.net/support/DoctorGL.exe.zip
For instruction follow below link:-
http://www.ononesoftware.com/support/607/
I am using EclipseMe on Ubuntu. I want an emulator that can emulate mouse movements on screen.
Is there an s60 emulator for linux?
Edit:
Does net beans has an in built emulator that can emulate mouse movement on device screen?
Netbeans uses the Sun Wireless Toolkit.
The JavaME emulator it contains can me made into a touchscreen emulator. Read the accompanying documentation, it should be as simple as setting a variable inside a configuration file before stating the emulator.
You can find the specification for MIDP (the top layer of the JavaME platform you're probably targetting) at http://jcp.org/en/jsr/detail?id=118
Look at the javax.microedition.lcdui.Canvas class, you will find several methods used to deal with "pointer". While they are more often used to handle touchscreen event, they also map to mouse/joystick clicks on emulators.
You can definitely get the MIDP pointerDragged events when running the emulator on Linux.
This is basic MIDP, no need for fancy JSR-226 (e-swt) support.
The Windows only Symbian Emulator (EPOC) is being scrapped for a QEMU based emulator that will run on all platforms. This will likely be available within 6 months or so.
At the moment, I run Windows XP inside VirtualBox on my Mac for Symbian development. It works fine, but is of course not the ideal solution.
The full symbian OS emulator with application interfaces for Java and Symbian C is windows based unfortunately.
I usually get a MS Windows Vista install disk and install that into a VM like VirtualBox and than install the symbian SDks on top of that..
Works best on those 4 core desktop 64-bit computers now on sale for $687 as you get access to full 8 gig ram and close to 1 terabyte hard drive..