<commit_before>---
layout: post
title:  "Using Qt Creator inside of a hardware accelerated Virtualbox image"
date:   2017-06-04 12:10:59 -0700
published: true
tags: [gl, arch, linux, oss, amd]
---

# Introduction

http://doc.qt.io/QtQuick2DRenderer/<commit_msg>Pump up the jam on Qt Creator black window bullshit<commit_after>---
layout: post
title:  "Using Qt Creator inside of a hardware accelerated Virtualbox image"
date:   2017-06-04 12:10:59 -0700
published: true
tags: [gl, vm, linux, oss, qt, qtcreator]
---

# Introduction

I recently had the joy of being handed a Mac laptop running QtCreator inside of a VM in order to demonstrate my 1337 QML skills. The VM was dog slow, and it was not hard to see why; GPU hardware acceleration was disabled. being a rocket scientist, one immediately enables video acceleration and is promptly rewarded with (a) black window(s) where Qt Creator's aspecto is meant to present itself. Awesome.

# Solution

Luckily there is a solution:

export QMLSCENE_DEVICE=softwarecontext

prior to running Qt Creator in your VM, and you are cooking with gas. (as documented [here](http://doc.qt.io/QtQuick2DRenderer/))

If it seems counter intuitive to you to enable hardware acceleration only to use software rasterization in the sole application you are running, then you are suffering from a sever case of over rationality. I suggest a beer and maybe ratifying it.
{'fraction_non_alphanumeric': 0.06933523945675482, 'fraction_numerical': 0.03002144388849178, 'mean_word_length': 4.426356589147287, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1775636', 'n_tokens_mistral': 432, 'n_tokens_neox': 381, 'n_words': 201}