Saillogger Community

Get a notification when a friend's boat leaves and when she arrives, and give your family ashore an easy way to follow yours. The AIS Fleet app is now on the App Store, free for iPhone and iPad. Here is what it does: Know when a boat you follow leaves and arrives Follow a boat, turn on notifications in the app, and her departures and arrivals reach you. They come without a sound and wait in Notification Center. Let family ashore follow your boat Keep your logbook with Saillogger? Once an AIS receiver has heard your boat, family and friends can follow her in the app by her MMSI, with no boat or Saillogger account of their own. Your Saillogger sharing settings decide whether they also read your journal and see the passage you are on. With the AIS Fleet switch on under Settings > Integrations in Saillogger, your boat keeps moving on their map whenever you have internet aboard, even where no AIS receiver can hear her. See the traffic around your anchorage Aboard, the app connects to your AIS receiver over the boat's Wi-Fi and, while the app is on screen, draws the boats it hears within seconds. What it hears also joins the AIS Fleet network, extending coverage where no shore station reaches, and you can pause that sharing. Earn Plus or Pro with your photos In one calendar month, use AIS Fleet to photograph three boats you have not photographed with it before. Once the photos are published, you hold Plus for the following month. Ten boats earn Pro. How it counts The app needs iOS 17 or later and uses the same account as aisfleet.com, so your follows, lists, fleets and messages are waiting when you sign in. Watching the map is free, following up to five boats is free, and the free plan does not expire. Plus and Pro are available in the app. On Android or a computer, use aisfleet.com in the browser. Joined the open beta earlier this month? Thank you for trying it. Please install AIS Fleet from the App Store now, because the TestFlight build stops opening when it expires. New since the beta: push notifications, lists, and photos that earn Plus or Pro. [image: app_store.svg] Download AIS Fleet from the App Store If you like the app, a rating on the App Store helps others find it. Have questions or ideas? Reply here and tell us how you are using it. Fair winds and following seas! The Saillogger Team

Tried the AI assistant built into the chrome dev console. It suggests a few different root causes related to the canvas size. I confirmed changing my display scale from 125% to 100% in windows 11 fixes the isssue on desktop and is probably why you don't see it on your side. Still broken on my Pixel 10 pro, but looks like it always worked on my Ipad 13 pro. If the canvas size is tied to the dimensions of the track, I've sailed from South Africa to the US and the Med, so that could be a factor? Here's what the AI says. Bug Report: GPU Crash & WebGL Overflow on High-DPR Devices Symptoms: Crash: Map displays a "white screen" or "unhappy face" icon (GPU process crash) on high-DPR devices (e.g., Pixel 10 Pro, or desktops with >100% scaling). Console Error: GL_INVALID_VALUE: glTexSubImage2DRobustANGLE: Offset overflows texture dimensions when switching layers. Reproducibility: Works at 100% scaling (DPR 1.0), but fails consistently at 125% (DPR 1.25) or mobile scales (DPR 3.0+). Root Causes Massive Canvas Allocation ($2^{25}$px): The element canvas.tl-head-canvas is attempting to set its width and height attributes to 33,554,432 ($2^{25}$). This is likely caused by a logic error where map coordinates or zoom levels are being multiplied by window.devicePixelRatio without being clamped to the viewport size. Why it fails on mobile: A Pixel 10 Pro has a high DPR (3.0–4.0). The math hits this $2^{25}$ limit significantly faster than on a 1.0 DPR screen. Sub-pixel Mismatch (DPR 1.25): At a 1.25 scale, a CSS width like 570px results in 712.5 physical pixels. The browser rounds the canvas to 712, but the WebGL engine (MapLibre/Mapbox) attempts to update a texture at the 712.5 offset. This "overflows" the actual 712px texture boundary, triggering the glTexSubImage2D error. Recommended Fixes Clamp Canvas Dimensions (Immediate Fix for Crash) Ensure that any code resizing the tl-head-canvas (or any overlay canvas) is clamped to the actual viewport size or the maximum texture size supported by the GPU. js // Example fix in the resize handler: const MAX_SIZE = gl.getParameter(gl.MAX_TEXTURE_SIZE) || 4096; canvas.width = Math.min(calculatedWidth, MAX_SIZE, window.innerWidth * window.devicePixelRatio); canvas.height = Math.min(calculatedHeight, MAX_SIZE, window.innerHeight * window.devicePixelRatio); Use code snippets with caution Normalize Container Dimensions To prevent the Offset overflows error, ensure the map container always has integer physical pixel dimensions. js // Force the container to an integer-friendly size const rect = container.getBoundingClientRect(); const dpr = window.devicePixelRatio; container.style.width = ${Math.floor(rect.width * dpr) / dpr}px; container.style.height = ${Math.floor(rect.height * dpr) / dpr}px; Use code snippets with caution Check Pointer-Events on Overlays The .tl-side container has pointer-events: none globally, but the buttons inside it do not consistently have pointer-events: auto applied, which can block interactions on some mobile browsers even if the crash is avoided.

Hi, thank you for the note. On tank volume: this was a bug on our side, not in your setup. The Conditions table on trip pages rounded tank readings to the nearest 100 L, and humidity and battery charge to the nearest 10%, so 0.083 m³ showed as 100 L. The figure on the live dashboard was correct. A fix is deployed, and nothing needs changing on your side. Motor time is a bit different. The two engines are not added together. Motoring is the time at least one engine is running. As example, if one engine ran for the first leg, the other around midday, and both for the arrival. So the boat can come under engine for close to 4 hours, while the engines logged 1.8 h and 2.4 h each. Each engine’s own hours are under Engine hours on the trip page.