I'm pretty sure this is an SU12 bug but in VR the LNM web served panel now shows all lines and markers in the tiniest scale. I think it's a web viewport issue which is telling LNM that the windows is far bigger than it really is, so LNM is generating an image for an enormous window which is getting shrunk to fit the actual space.

Hopefully MSOBO will fix this soon but does anyone know a webby workaround? Something to do with viewports would be cleaner otherwise hack around with these function in scripts.js

 

function mapWidth() {
  return Math.max(document.getElementById('mapcontainer').offsetWidth, 128);
}

function mapHeight() {
  return Math.max(window.innerHeight - document.getElementById('header').offsetHeight - 50, 128);
}

2 hours ago, Spit40 said:

I'm pretty sure this is an SU12 bug

It is. This is probably related to this issue

https://forums.flightsimulator.com/t/3rd-party-applications-toolbars-scaling-broken-for-vr-in-su12/582576/2

It was reported by me and others early in the beta, and acknowledged but not taken care of so far.

FSKneeboard and Sky4Sim already released workarounds to keep their apps working.

Kind regards, Michael

45 minutes ago, pmb said:

It is. This is probably related to this issue

https://forums.flightsimulator.com/t/3rd-party-applications-toolbars-scaling-broken-for-vr-in-su12/582576/2

It was reported by me and others early in the beta, and acknowledged but not taken care of so far.

FSKneeboard and Sky4Sim already released workarounds to keep their apps working.

Kind regards, Michael

Thanks Michael, yes I saw sky4sim mention it. I downloaded the fix but he encrypts/encodes his javascript so I couldn't see what he did.

I found something that is promising but I don't have time to see this through just now or for a few days so I'll leave it here if anyone wants to experiment.

 

    var realPixelsPerCSSPixel = /*devicePixelRatio ||*/ 1;
     realPixelsPerCSSPixel = 0.2; // Added by me

 

The first line is in the file scripts.js in the 2021-a subfolder of LNM. The line after is added by me with my guess at 0.2 which seems to make a difference but not sure if 0.2 is the best value to get things right again

Edited March 23, 20233 yr by Spit40