Doc: Update the FAQ

The Welcome mode is no longer implemented using Qt Quick 2, so the
problem arises later, when opening Qt Quick Designer or QML Profiler.

Change-Id: Ifbe50bdb9cfc1709842413d271d96378549eb673
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2018-06-01 10:20:29 +02:00
parent 071a09f312
commit af1bd287a8

View File

@@ -1,6 +1,6 @@
/****************************************************************************
**
** Copyright (C) 2016 The Qt Company Ltd.
** Copyright (C) 2018 The Qt Company Ltd.
** Contact: https://www.qt.io/licensing/
**
** This file is part of the Qt Creator documentation.
@@ -39,72 +39,6 @@
\section1 General Questions
\b {\QC only shows a blank window, a dialog complaining about missing OpenGL support, or crashes on startup. What's going wrong?}
Some parts of \QC use Qt Quick 2, which relies on OpenGL API for
drawing. The most prominent use of Qt Quick 2 is in the Welcome mode, but it's
also used for the \QMLD, and the QML Profiler.
Unfortunately the use of OpenGL can cause problems, especially in remote setups
and with outdated drivers. You can quickly check whether this is your problem by:
\list
\li Launching \QC with Welcome mode disabled ( \c{-noload Welcome} on
command line).
\li Checking the console or the Windows debugger log for OpenGL-related error messages.
\endlist
The fixes and workarounds differ, depending on your setup. As a last resort you
can disable the affected plugins.
\e{Virtual Machines}
Try to enable \e{3D acceleration} in your virtual machine's settings. For VirtualBox,
also make sure you have installed the Guest Addons, including experimental
\e{Direct3D support}.
\e{Windows}
Check whether \QC has been compiled with OpenGL/Desktop, or ANGLE as
a backend. The official binaries are always built with ANGLE (a library that
maps OpenGL ES API to DirectX).
\list
\li ANGLE backend: This requires a Windows version newer than Windows XP. If you
have problems, try updating your graphics drivers or update your
DirectX version. Run \c dxdiag.exe to check whether \e{Direct3D Acceleration}
is indeed enabled.
\li OpenGL backend: Make sure your graphics driver supports OpenGL 2.1 or newer.
Try to update your graphics driver.
\endlist
\e{Unix}
Run \c glxgears for a quick check whether OpenGL works in general. Check output of
\c glxinfo to get more details like the OpenGL driver and renderer (search for 'OpenGL'
in the application's output).
If you are using the Mesa driver, you can force OpenGL to be rendered in software
by setting the \c LIBGL_ALWAYS_SOFTWARE environment variable.
\e{Disabling plugins}
You can disable the \QC plugins, at the expense of losing functionality:
\list
\li Launch \QC from command line, with
\c {-noload Welcome -noload QmlProfiler -noload QuickDesigner} arguments.
\li Disable the plugins permanently by selecting \uicontrol Help > \uicontrol{About Plugins}.
\endlist
\b {How do I reset all \QC settings?}
@@ -143,6 +77,66 @@
\include widgets/creator-faq-qtdesigner.qdocinc qt designer faq
\section1 QML and Qt Quick Questions
\b {What should I do when \QC complains about missing OpenGL support?}
Some parts of \QC, such as \QMLD and QML Profiler, use Qt Quick 2, which
relies on OpenGL API for drawing. Unfortunately, the use of OpenGL can cause
problems, especially in remote setups and with outdated drivers. In these
cases, \QC displays OpenGL-related error messages on the console or records
them in the Windows debugger log.
The fixes and workarounds differ, depending on your setup. As a last resort,
you can disable the affected plugins.
\e{Virtual Machines}
Try to enable \e{3D acceleration} in your virtual machine's settings. For
VirtualBox, also make sure you have installed the Guest Addons, including
experimental \e{Direct3D support}.
\e{Windows}
Check whether \QC has been compiled with OpenGL/Desktop, or ANGLE as
a backend. The official binaries are always built with ANGLE (a library that
maps OpenGL ES API to DirectX).
\list
\li ANGLE backend: This requires a Windows version newer than Windows XP.
If you have problems, try updating your graphics drivers or update
your DirectX version. Run \c dxdiag.exe to check whether
\e{Direct3D Acceleration} is indeed enabled.
\li OpenGL backend: Make sure your graphics driver supports OpenGL 2.1 or
newer. Try to update your graphics driver.
\endlist
\e{Unix}
Run \c glxgears for a quick check whether OpenGL works in general. Check the
output of \c glxinfo to get more details like the OpenGL driver and renderer
(search for \e OpenGL in the application's output).
If you are using the Mesa driver, you can force OpenGL to be rendered in
software by setting the \c LIBGL_ALWAYS_SOFTWARE environment variable.
\e{Disabling plugins}
You can disable the \QC plugins, at the expense of losing functionality:
\list
\li Launch \QC from command line, with the
\c {-noload QmlProfiler -noload QuickDesigner} arguments.
\li Disable the plugins permanently by selecting \uicontrol Help >
\uicontrol{About Plugins}.
\endlist
\section1 Help Questions
\b {The Qt API Reference Documentation is missing and context help does