Enterprise 3D Project

A guy called Jason has decided to create the entirety of the USS Enterprise NCC-1701-D in the Unreal Game Engine.

I felt this is something that definitely needs as much as attention as possible. Everyone should check out the Enterprise 3D Project

How to start “Hearts of Darkness” quest middle step “Stop Tanval” (Elder Scrolls Online)

TLDR: Go to Kragenmoor to the Grandmsters Palace and find Grandmaster Omin Dres to begin the quest Aggressive Negotiations.

Elder Scrolls Online on consoles has an achievement/trophy called Hero of Ebonheart which requires you to complete all the in game achievements relating to the Ebonheart Pact.

As I was checking through the list of ones I completed, I noticed that for the achievement Hearts of Darkness, the middle step – Stop Tanval from unleashing the second Brother of Strife – was incomplete. When I checked the map there were no black markers normally indicative of an incomplete area, nor did I have any incomplete quests in Stonefalls.

It turns out there is short series of side quests that are easy to miss in the Kragenmoor area starting with Aggressive Negotiations. This eventually leads to To the Tormented Spire which adds the Tormented Spire as a location to your map. Complete this quest line completes the middle part of the Hearts of Darkness achievement.

[SOLVED] System.ExecutionEngineException: Attempting to JIT compile method

TLDR: Check multiple references to the same nuget package are all on the same version if you use the Mono linker.

Since my ability to post regularly on things I’m interested in is not great, I figured I could at least post stuff that might be useful.

I recently upgraded a Xamarin iOS app from the “classic” (32bit only) API to the Unified API. After doing so I got the error message:

System.ExecutionEngineException: Attempting to JIT compile method

.

This is caused by the Xamarin (Mono) linker removing code that is only referenced dynamically. The usual solution is to let the compiler know somehow that you are using the code (using a Preserve attribute if it’s your own code or something like MvvmCross’s LinkerPleaseInclude.cs otherwisr).

In my case, this did not fix the problem. It turns out the Unified API upgrade was a red herring. I had also updated a few nuget packages at the same time. One of them was used in several projects, but I’d missed updating one of them (so I had Project A using v1 of a package and Project B using v2 of a package). This meant my efforts to stop the linker from removing some stuff only worked on one version of the package.