nicky9499

Gday, I've encountered new issue of vmsACARS unable to resume flight. This functionality was working well up until recently (last time this feature was used was about 3 months ago). No changes to sim or operating system during the same time period. Can anyone help to make sense of the following entries in log please? 09-21 00:29:58|INFO; Resuming flight, in state: Approach 09-21 00:29:58|INFO; Starting PIREP, sim type=Prepar3d 09-21 00:29:58|INFO; Resume, calculating distance, curr=N037° 25.02', W122° 14.53', last=N037° 24.09', W122° 16.28' 09-21 00:29:58|INFO; Resuming, distance from last report: 1.67mi 09-21 00:30:17|ERROR; UnhandledException UncaughtException::System.IO.IOException;Stacktrace at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, Int64 preallocationSize) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize) at NLog.Internal.FileAppenders.BaseFileAppender.TryCreateFileStream(Boolean allowFileSharedWriting, Int32 overrideBufferSize) at NLog.Internal.FileAppenders.BaseFileAppender.TryCreateDirectoryFileStream(Boolean allowFileSharedWriting, Int32 overrideBufferSize) at NLog.Internal.FileAppenders.BaseFileAppender.CreateFileStream(Boolean allowFileSharedWriting, Int32 overrideBufferSize) at NLog.Internal.FileAppenders.CountingSingleProcessFileAppender..ctor(String fileName, ICreateFileParameters parameters) at NLog.Internal.FileAppenders.CountingSingleProcessFileAppender.Factory.NLog.Internal.FileAppenders.IFileAppenderFactory.Open(String fileName, ICreateFileParameters parameters) at NLog.Internal.FileAppenders.FileAppenderCache.CreateAppender(String fileName, Int32 freeSpot) at NLog.Internal.FileAppenders.FileAppenderCache.AllocateAppender(String fileName) at NLog.Targets.FileTarget.WriteToFile(String fileName, ArraySegment`1 bytes, Boolean initializedNewFile) at NLog.Targets.FileTarget.ProcessLogEvent(LogEventInfo logEvent, String fileName, ArraySegment`1 bytesToWrite) at NLog.Targets.FileTarget.Write(LogEventInfo logEvent) at NLog.Targets.Target.Write(AsyncLogEventInfo logEvent) at NLog.Targets.Target.WriteAsyncThreadSafe(AsyncLogEventInfo logEvent) at NLog.Targets.Target.WriteAsyncLogEvent(AsyncLogEventInfo logEvent) at NLog.LoggerImpl.WriteToTargetWithFilterChain(Target target, FilterResult result, LogEventInfo logEvent, AsyncContinuation onException) at NLog.LoggerImpl.Write(Type loggerType, TargetWithFilterChain targetsForLevel, LogEventInfo logEvent, LogFactory logFactory) at NLog.Logger.WriteToTargets(LogEventInfo logEvent, TargetWithFilterChain targetsForLevel) at NLog.Logger.WriteToTargets(LogLevel level, String message) at NLog.Logger.Info(String message) at Acars.App..ctor() at Acars.App.Main() Thank you. Regards, Nick

G'day guys, May I ask if it is possible to do any sort of processing on basemap colors for the map used in phpvms/vmsacars? I have read the following documentation: https://docs.phpvms.net/customize/maps The default OSM.Mapnik is great especially since it shows taxiway designations at many airports - useful as a mini-EFB for aerodrome navigation. However we also like maps like Stadia.Dark with a dark gray theme which goes very well with vmsacars dark mode. However it doesn't contain airport data. Ideally we'd like to tweak the colors of OSM.Mapnik into something like Stadia.Dark, even a simple invert seems like it would suffice. Thanks in advance for the advice. Cheers, Nick

Hi DH, thanks for the come back. No, we do not allow free flights, all flights are booked in the crew center first before loading it into acars. I have checked the database entries and links to each other, they all check out, so I can't figure out what is wrong. In the above image, you can see id=1 is correct. SVAG is id=8. Below is the flight under "flights" table: Edit: the flight itself under "pireps" table did list an airline_id=8 for that flight. I'm just very puzzled how it was even possible for that pilot.

G'day gents, I'm running 7.0.0-dev+220225.9d368e and Disposable. Disclaimer that they both need to and will be updated urgently so if this issue can only be solved as such then kindly advise and disregard this thread. Basically as the screenshots show, I have a slight (SIA/SQ) that is showing up incorrectly as SVAG. Because our VA runs multiple subsidiaries (eg. SIA/TGW), we place all pilots under the shell airline "SVAG" but there are no actual flights listed under this. However, one particular flight has caught my attention multiple times recently showing the latter prefix. Is there any way to correct this? It's very minor and only a slight aesthetic/OCD-level annoyance, but if an easy fix is possible I'd like to do it. Thanks in advance.

Thank you Nabeel and DH for the long and short term solutions, respectively.

Not much, to be honest. The typeface has to be of contrasting color to the background, and a single "in between" for something drastically different like black/white doesn't look good in either. We have a white version of the logo specifically for this sort of situation: Alternatively, would it be possible to introduce a setting to lock acars to light/dark mode?

G'day Nabeel, There was a recent update that allows acars UI to match the Windows dark mode setting - my night owl virtual pilots with secondary monitors are truly grateful for this implementation. However, there is a minor issue wherein we only have 1 logo setting which can only match either Windows' light or dark mode. Would it be possible to allow two versions to be uploaded, both of which correspond to phpvms' light/dark modes please?

Hi gents, Myself and a couple pilots encounter the following error message mid-flight on occasion. We can dismiss it and carry on normally, but I'd like to check what might be causing it and possible fixes. phpVMS: 7.0.0-dev vmsACARS: 1.0.0.1989 cPanel: 100.0 build 7 Apache: 2.4.52 PHP: 7.4.27 MySQL: 10.3.32-MariaDB

Hi guys, I'm running phpVMS v7.0.0-dev and DH's theme (don't know where to check which version). On all the frontend pages, some flights have appended information in their flight designation. Usually multi-leg flights or those that are part of a tour. Is there any way to hide these?

Hi Nabeel, thanks for the reply and insight! An extension of your idea - I am going along the K.I.S.S. school of thought here - why not just straight up not display any segment that crosses the date line? Since update interval is relatively frequent in vmsACARS, I doubt anyone would be complaining that a very short stretch of their flight path over the big open sea is missing.

G'day DH and web-savvy friends, I'd like to seek advice and suggestions on how best to handle the following situation where there is limited space due to a small browser window size - is there a graceful way to display part or all of the information? Technically, it isn't the window that is small, just part of the theme that is not utilizing the full width, it seems like an invisible column on the top half. (Please see attachments.)

G'day Nabeel and dev team, I'm writing to propose a suggestion to improve how the flight path is displayed when crossing the date line (or basically one side of the global map to the other). Right now its behavior is to draw an extremely long line right across to connect to the "other side". Example, when crossing the Pacific Ocean: I am not a developer by trade, so please excuse me if this is simpler said than done. My suggestion is to simply have a rule for each drawn segment: if, segment length = x then, do not draw where x is an extremely large distance such as 1000nm, which would be highly unlikely for any flight to cover without at least crossing a waypoint or navaid. This solution would leave a gap between the edge of the map and the waypoint closest to it for planned path (yellow), but the tracked path (white) will be accurate. Please let me know your thoughts or comments on this. Thank you.

Hi ProAvia, I DM-ed Nabeel and he replied earlier in unblocking my ID. Sincere thanks to both of you and yes I do have messaging and security settings locked down now after the spam incident.

Seems perfect. I'll try to get that to work on my end, thank you DH.

Hello DH, Thank you, sincerely, for your effort in going through some of the logs and the resulting advice. The pop-up box says, in full, my version is 7.0.0-dev. That is the whole build number. Is this outdated? I do have "addons/modules" and "type ratings" in the menu. I just popped by the Downloads section to grab the latest build, which also happens to be in an archive named phpvms-7.0.0-dev.zip What I didn't mention earlier (as it didn't seem significant then) was that our VA recently had a team member suddenly depart without a proper handover. He was the only one working on modifications to the phpVMS/Disposable pilot site right after an upgrade from v5 to v7 which was also pushed through by him even though we were not necessarily fully ready. These errors started happening around the same time he left which coincided with hosting outages, so we initially thought the latter was the cause. Your investigations reveal thus far we may have had placed a little too much trust in his competency and trustworthiness. I'll try to chip away at these faults one at a time and post back for advice on specific issues if necessary. Once again thank you. Edit: so, just to be clear what I'm dealing with here - I have (possibly) the latest version of phpVMS, working alongside vmsACARS which is compatible but also Disposable Theme v2 which is technically incompatible with this build of phpVMS. Hence my first course of action would be to try to upgrade Disposable Theme to v3....?