Documentation

Errors and log lines

Something stopped, or a report’s log shows a line you do not understand. Search for the words in the message. Each entry says what it means, what to try, and how sure we are.

Starting a game

"Pairing file needed"

You see: Pairing file needed

The pairing file lets Porthole switch JIT on, which games need to run at speed. Without it the game cannot start.

Try:

  • On iOS 27 or later: in the setup guide tap Create it on this device, then open Settings > Privacy & Security > Developer Mode > "Pair with Porthole" and type the six-digit code Porthole shows.
  • On earlier iOS: make the file once on a computer with a free pairing tool such as iloader or Jitterbug, move it to the device and choose it in Porthole.

From the Help page.

The tunnel says "connecting" and then "disconnected" after an update

You see: [tunnel] ... connecting, then disconnected

iOS sometimes keeps old information about the app's helper after an update.

Try:

  • Restart the device. Your games and settings are not affected and you do not need to reinstall.

Seen repeatedly; restarting fixes it.

"Large address space is not allowed" in the install check

You see: [install] note: Large address space is not allowed

This copy of Porthole was signed without the permission that lets games map the big block of address space the engine reserves for them. Some games will not start, or close shortly after they do. Many games run fine without it, so the line is a note, not always a fault.

Try:

  • If a game closes at start, sign Porthole again with a profile that carries the extended virtual addressing capability (the install check in Settings says whether your profile has it).

The wording is the app's own; whether it is the cause of a given crash has to be read from that game's log.

Steam

"Steam did not accept the saved sign-in for downloads"

You see: Steam: the sign-in for downloads was refused (result 5). [cloud] skipped: Steam did not accept the saved sign-in for downloads. Sign in for downloads again.

The sign-in Porthole saved for downloads and Steam Cloud has expired or was refused, so cloud saves are skipped for that run. The game itself can still start.

Try:

  • Open Settings > Steam and sign in for downloads again.

The log line says so itself.

Steam sign-in or downloads fail on one network only

You see: TLS or connection errors to Steam

Some work and school networks block Steam.

Try:

  • Try another network or a mobile connection. If it works there, the network was the cause.

From the Help page.

Graphics

"Minimum required feature level D3D_FEATURE_LEVEL_12_0 not supported"

You see: Maximum supported feature level: D3D_FEATURE_LEVEL_11_1 / Minimum required feature level D3D_FEATURE_LEVEL_12_0 not supported

The game's Direct3D 11 mode asks for feature level 12_0, and Porthole's Direct3D 11 layer reports 11_1 at most. The game then shows its own error and closes. A setting cannot raise that level.

Try:

  • Start the game in its DirectX 12 mode instead. If you added a -dx11 launch argument, remove it.
  • Games whose only mode needs feature level 12_0 on Direct3D 11 cannot run through that layer.

Seen with Dying Light: The Beast launched with -dx11; its DirectX 12 mode starts.

Black screen and 0 FPS after the game ran well for a while (DirectX 12)

You see: Queue::Wait: fence ... never reached N in 5 s (at 0); continuing

A command queue is waiting for a fence that nothing ever signalled, so the game stops drawing frames. The process is still alive: sound may carry on. One known cause is a game that writes a marker value with WriteBufferImmediate and then waits for it (see the next entry).

Try:

  • Look just before the first Queue::Wait line in the report log for unimplemented: ... WriteBufferImmediate. If it is there, add the engine line write-buffer-immediate = 1 to the game's engine lines and start it again.
  • If memory warnings (mem-pressure CRITICAL) come just before, raise the game's Swap or lower its graphics quality.
  • Send a problem report from Settings > Report a problem if it keeps happening.

The fence line is a symptom, not a cause. The WriteBufferImmediate connection is likely but not yet confirmed for every game.

"unimplemented: ID3D12GraphicsCommandList7::WriteBufferImmediate"

You see: [madeira-d3d12] unimplemented: ID3D12GraphicsCommandList7::WriteBufferImmediate

The game called a Direct3D 12 function that writes a small value from the GPU. By default Porthole ignores it, because writing it is switched off. A game that waits for that value will wait forever.

Try:

  • Add write-buffer-immediate = 1 to the game's engine lines (game settings > Starting > This game's engine lines). The log then says write-buffer-immediate = 1 (opt-in).

The option is part of the engine and is on in the recommended setup of other games. Whether it fixes a particular game has to be tried.

Memory

"[mem-pressure] CRITICAL"

You see: [mem-pressure] CRITICAL: app 6723 MB, free 1469 MB, gpu 4536 MB

Porthole is close to the memory iOS lets one app use. The game may stutter, freeze, or be closed by iOS without warning. The numbers say how much the app, the free memory and the graphics memory are using.

Try:

  • Open the game's settings and raise Swap; a wide swap coverage helps games with many small allocations.
  • Lower the game's own texture and graphics quality: graphics memory is a large part of the total.
  • Close other apps before you start.

General guidance from the Help page; a game that needs more memory than the device can give cannot be fixed with a setting.

Log lines that are not the problem

"[ERR] [no-footprint] pool applied=false"

You see: [no-footprint] pool-RW-alias: ALL 4 variants refused - pool stays jetsam-counted

Porthole tried to keep its code memory out of the count iOS uses to decide when to close an app, and iOS refused all four ways. The line is marked ERR but the game starts normally; the memory just stays counted.

Try:

  • Nothing. It appears in logs of games that run.

It is in every log we have read, including those of games that played.

"Assertion Failed: Failed to load video64.dll"

You see: src\public\tier1\interface.h (271) : Assertion Failed: Failed to load "video64.dll"

It comes from Valve's own code that starts with the game. It appears in logs of games that went on to run.

Try:

  • Nothing, unless the game also fails to start; then read the lines after it.

Seen in logs of games that played.