Fatal Signal 11 , LibGDX 1.0 and GenyMotion

I was encountering the issue on simple libgdx programs crashing out on GenyMotion vm with similar messages like


"Fatal signal 11 (SIGSEGV) at 0x97281008 (code=2), thread 2496 (Thread-183)"


which seems to be caused by any drawing calls... isolated each call and still had the same issue. Program will just crash out with signal 11 after a while.

Turns out the quick fix is to have vmSafeMode in AndroidManifest.xml.

    <application

        android:allowBackup="true"

        android:vmSafeMode="True"

        android:icon="@drawable/ic_launcher"

        android:label="@string/app_name"

        android:theme="@style/GdxTheme" >

How to develop with Titanium SDK and Genymotion in OSX

I was puzzled why Titanium SDK wouldn't detect a Genymotion VM even though I've done a ADB connect and "adb devices" can list the device. That is how I debug my android setup in Windows( it's slightly different as the IDE is on a separate network - will cover in the upcoming post).


Turns out that for Mac, if you're running Titanium SDK and GenyMotion all on the same machine, you need to launch a terminal and issue

ti config genymotion.enabled true

Refresh the devices and you will find Genymotion vms listed in the Android Emulator group.

Strange... it's listed differently from my Windows setup (appears as a device).

OSX Rift and WINE

Rift doesn't have a native client on OSX. Oh well.


I didn't get very far with WineSkin so I thought I'll try PlayOnMac instead. I was using PlayOnLinux when I was using Ubuntu previously.


Install PlayOnMac 4.2.2 (http://www.playonmac.com/en/download.html)

Using PlayOnMac , pull the latest wine binary for POL.(Tools->Manage Wine Versions)

Installed VCRun2005, VCRun2008 and d3dx9

Set the display settings to

GLSL Support : Enabled

Direct Draw Render: OpenGL

Offscreen Rendering Mode: FBO

Strict Draw Ordering: Enabled

I had no luck launching the installer found on the site( it worked in WineSkin hours before however).


I used this patcher instead..

http://update2.triongames.com/patcher/public/Rift_LIVE_Patcher_setup.exe


The installer will run and exit, run it again to patch the patcher(you may encounter a few more crashes but it should work in the end)


The final shortcut installed should be the main launcher for the client.

Java development and OSX

During my app development on OSX, the somewhat strange Java situation surfaced with some of the products.

Titanium SDK needs Java 6 to start, Java 1.7 won't do or the IDE will throw an error message. This means the Apple 1.6 version is needed, if you have Oracle JDK installed, you will need to download Java 6 from Apple's site:

Java for OS X 2013-005

http://support.apple.com/kb/DL1572?viewlocale=en_US


IntelliJ runs on  Java 1.6, however LibGDX requires Java 7. Importing Gradle project will fail with a RoboVM error. Fortunately there is a way to force IntelliJ to use Java 7 runtime.

http://www.gamefromscratch.com/post/2014/04/03/Troubleshooting-IntelliJLibGDXRoboVMGradle-issues-on-Mac-OS.aspx

Setting JAVA_HOME for OSX Mavericks

I have a copy of Oracle JDK 7 installed in my system.

Downloaded Maven2 from Homebrew and realized that Java_Home wasn't set correctly.

The fix:

To get the correct path, you will need to execute /usr/libexec/java_home to obtain the path.

To automatically set JAVA_HOME in terminal every time, append

export JAVA_HOME=`/usr/libexec/java_home`

to the end of ~/.bash_profile

You should be able to execute mvn in a new terminal.

Activate Go Syntax highlighting for VIM in Ubuntu 14.04

This seems to be the shortest step to enable Go's syntax highlighting out of the box on Ubuntu 14.04 server.

I haven't tried the desktop edition but it should be similar.


Install  vim-syntax-go

sudo apt-get install vim-syntax-go

Create the .vim directory in your home directory



mkdir .vim
mkdir ~/.vim/syntax
cp /usr/share/vim/addons/syntax/go.vim ~/.vim/syntax/   

mkdir ~/.vim/ftdetect 

cp /usr/share/vim/addons/ftdetect/gofiletype.vim ~/.vim/ftdetect/

PaintTool SAI and Windows 8.1

Updated PC to Window  8.1 and found that PaintTool SAI wouldn't start without UAC kicking in no matter what I changes I make to the NTFS permissions..

Found the solution for it via http://nerdanswer.com/answer.php?q=359258

Create a batch file :

set __COMPAT_LAYER=RUNASINVOKER
start .sai.exe


as a workaround.