Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

xPilot 1.3.17-Alpha Now Available


Justin Shannon
 Share

Recommended Posts

Justin Shannon
Posted
Posted (edited)

EDIT: For those who use VR and are having issues with X-Plane crashing, you may revert back to v1.3.15 until the issue is resolved. You can obtain the download directly from here: http://xpilot.clowd.io/installers/alpha/xPilot-Setup-1.3.15.exe

----------------------------------

Version 1.3.17-Alpha of xPilot is now available for download from the web site, or via the automatic update utility built into the pilot client (if you have the "Alpha" update channel selected in the settings). This version includes the enhancements that were added in the 1.3.16 version.

The following items were changed, added or fixed in this version:

  • Added dual radio volume control capability. This means you can now control the radio volume via the volume knobs separately for COM1 and COM2. The volume multiplier has also been slightly increased since the initial release in 1.3.16.
  • Fixed unhandled exception when downloading network server list.
  • Added transparent notification window that appears at the top of the X-Plane window. This replaces the automatic popup of the radio text message window (now known as the "Text Message Console").
  • Text Message Console command has been renamed from xpilot/toggle_text_window to xpilot/toggle_text_message_console.
  • Added network callsign data (xpilot/login/callsign). The dataref value is empty when not connected to the network.
  • Added COM1/COM2 radio receive indicator datarefs (xpilot/audio/com1_rx and xpilot/audio/com2_rx). These datarefs replace the previous ("xpilot/audio/rx") dataref. A value of 1 indicates radio audio is being received. A value of 0 indicates no audio is being received.
  • Update imgui library

It is very important that you close X-Plane completely before installing xPilot. Failure to do so will prevent xPilot from being installed correctly.

Edited by Justin Shannon
  • Like 1

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Nico Paetzold
Posted
Posted

Finally Volume Control 😍
It's getting better and better with every Update you publish

Great Work

  • Like 1
Link to comment
Share on other sites

Richard Asberg
Posted
Posted

Just updated to 1.3.17 and going into the audio settings where I found the new volume controls, they were all the way to the left (0) for both COM1 and COM2.

Figured it was because these settings are new and require you to reset the volume. So I did but after moving both sliders to 50%, the OK button nor the Apply button got activated. Meaning the only option I had was to press the Close button. Still, when going back into audio settings after this, it seems like the changes got saved...?

1481246394_Greenshot2020-07-0110_51_29-X-Plane.thumb.jpg.39b55167b4a19b835fde7ba8964ae5ea.jpg

Richard Åsberg

Link to comment
Share on other sites

Richard Asberg
Posted
Posted

Another issue, just got this:

1540915097_Greenshot2020-07-0111_24_06-xPilot-RYR888.jpg.2f2c853dbc4c4d1c10500ebadb8891e2.jpg

And here is the full message if of any use to you. This happened after I restarted xPilot and reconnected to the network when X-Plane was already running. Not sure if that was the trigger...?

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at an.h(Object A_0, a7 A_1)
   at Appccelerate.EventBroker.Handlers.EventBrokerHandlerBase.HandleSubscriberMethodException(TargetInvocationException targetInvocationException, IEventTopicInfo eventTopic)
   at Appccelerate.EventBroker.Handlers.OnUserInterfaceAsync.<>c__DisplayClass1.<Handle>b__0(Object data)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
xPilot
    Assembly Version: 1.3.17.0
    Win32 Version: 1.3.17.0
    CodeBase: file:///F:/xPilot/xPilot.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
Ninject
    Assembly Version: 3.3.3.0
    Win32 Version: 3.3.3.0
    CodeBase: file:///F:/xPilot/Ninject.DLL
----------------------------------------
GeoVR.Client
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.DLL
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Ninject.Extensions.Factory
    Assembly Version: 3.3.2.0
    Win32 Version: 3.3.2.0
    CodeBase: file:///F:/xPilot/Ninject.Extensions.Factory.DLL
----------------------------------------
Castle.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///F:/xPilot/Castle.Core.DLL
----------------------------------------
Appccelerate.EventBroker
    Assembly Version: 3.15.0.0
    Win32 Version: 3.15.0.0
    CodeBase: file:///F:/xPilot/Appccelerate.EventBroker.DLL
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
DynamicProxyGenAssembly2
    Assembly Version: 0.0.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///F:/xPilot/Castle.Core.dll
----------------------------------------
DynamicProxyGenAssembly2
    Assembly Version: 0.0.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///F:/xPilot/Castle.Core.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
    Assembly Version: 0.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Appccelerate.Fundamentals
    Assembly Version: 2.8.0.0
    Win32 Version: 2.8.0.0
    CodeBase: file:///F:/xPilot/Appccelerate.Fundamentals.DLL
----------------------------------------
System.Runtime
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
Gma.System.MouseKeyHook
    Assembly Version: 5.6.130.0
    Win32 Version: 5.6.130.0
    CodeBase: file:///F:/xPilot/Gma.System.MouseKeyHook.DLL
----------------------------------------
XPlaneConnector
    Assembly Version: 1.2.0.0
    Win32 Version: 1.2.0.0
    CodeBase: file:///F:/xPilot/XPlaneConnector.DLL
----------------------------------------
GeoVR.Shared
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Shared.DLL
----------------------------------------
netstandard
    Assembly Version: 2.0.0.0
    Win32 Version: 4.8.4084.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/netstandard/v4.0_2.0.0.0__cc7b13ffcd2ddd51/netstandard.dll
----------------------------------------
GeoVR.Connection
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Connection.DLL
----------------------------------------
NLog
    Assembly Version: 4.0.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
Concentus
    Assembly Version: 1.1.6.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
System.Runtime.Extensions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Extensions/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Extensions.dll
----------------------------------------
NetMQ
    Assembly Version: 4.0.0.1
    Win32 Version: 4.0.0.1
    CodeBase: file:///F:/xPilot/NetMQ.DLL
----------------------------------------
AsyncIO
    Assembly Version: 0.1.25.0
    Win32 Version: 0.1.25.0
    CodeBase: file:///F:/xPilot/AsyncIO.DLL
----------------------------------------
SharpDX.DirectInput
    Assembly Version: 4.2.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///F:/xPilot/SharpDX.DirectInput.DLL
----------------------------------------
SharpDX
    Assembly Version: 4.2.0.0
    Win32 Version: 4.2.0
    CodeBase: file:///F:/xPilot/SharpDX.DLL
----------------------------------------
NAudio
    Assembly Version: 1.9.0.0
    Win32 Version: 1.9.0.0
    CodeBase: file:///F:/xPilot/NAudio.DLL
----------------------------------------
Newtonsoft.Json
    Assembly Version: 12.0.0.0
    Win32 Version: 12.0.2.23222
    CodeBase: file:///F:/xPilot/Newtonsoft.Json.DLL
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
Microsoft.CSharp
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll
----------------------------------------
RestSharp
    Assembly Version: 106.0.0.0
    Win32 Version: 106.10.1.0
    CodeBase: file:///F:/xPilot/RestSharp.DLL
----------------------------------------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Dynamic
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll
----------------------------------------
System.IdentityModel.Tokens.Jwt
    Assembly Version: 5.6.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
Microsoft.IdentityModel.Tokens
    Assembly Version: 5.6.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
Microsoft.IdentityModel.Logging
    Assembly Version: 5.6.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
Microsoft.IdentityModel.JsonWebTokens
    Assembly Version: 5.6.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
MessagePack.CryptoDto
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/xPilot/MessagePack.CryptoDto.DLL
----------------------------------------
MessagePack.Annotations
    Assembly Version: 2.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///F:/xPilot/GeoVR.Client.dll
----------------------------------------
System.Runtime.InteropServices.RuntimeInformation
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.InteropServices.RuntimeInformation/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.InteropServices.RuntimeInformation.dll
----------------------------------------
System.Memory
    Assembly Version: 4.0.1.1
    Win32 Version: 4.6.27617.02
    CodeBase: file:///F:/xPilot/System.Memory.DLL
----------------------------------------
System.Runtime.CompilerServices.Unsafe
    Assembly Version: 4.0.4.1
    Win32 Version: 4.6.26919.02
    CodeBase: file:///F:/xPilot/System.Runtime.CompilerServices.Unsafe.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

Richard Åsberg

Link to comment
Share on other sites

Kevin Townsend
Posted
Posted (edited)

I installed version 1.3.17 a short while ago
I see issues with the CSL. All my liveries for Vatsim members are displaying as Boeing generic.
In confirming the CSL path I was initially confused, so I added a copy of my Bluebell CSL collection into the root of Drive C

This confirmed my theory. Drive lettering is amiss.
Drive C  and its contents appear in the xPilot preferences dialogue as D, Drive D  appears as E etc

xPilot1.png

Confirm: Whatever I try all Vatsim members are appearing in Generic Boeing Liveries still.....

Edited by Kevin Townsend
added info

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
27 minutes ago, Kevin Townsend said:

I installed version 1.3.17 a short while ago
I see issues with the CSL. All my liveries for Vatsim members are displaying as Boeing generic.
In confirming the CSL path I was initially confused, so I added a copy of my Bluebell CSL collection into the root of Drive C

This confirmed my theory. Drive lettering is amiss.
Drive C  and its contents appear in the xPilot preferences dialogue as D, Drive D  appears as E etc

xPilot1.png

Confirm: Whatever I try all Vatsim members are appearing in Generic Boeing Liveries still.....

Hi Kevin,

The [D] next to each entry in the list represents "directory". The file browser shows that you are in the C drive at the top of the file browser window (C: *).

What do you mean by Drive D appears as Drive E? Can you provide a screenshot to show this?

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
4 hours ago, Richard Asberg said:

Just updated to 1.3.17 and going into the audio settings where I found the new volume controls, they were all the way to the left (0) for both COM1 and COM2.

Figured it was because these settings are new and require you to reset the volume. So I did but after moving both sliders to 50%, the OK button nor the Apply button got activated. Meaning the only option I had was to press the Close button. Still, when going back into audio settings after this, it seems like the changes got saved...?

The volume slider value is read from the sim/cockpit2/radios/actuators/audio_volume_com1/com2 datarefs. If the volume knobs in the aircraft were initially turned down (set to zero), then that is why the sliders were set to 0. It's also possible that the aircraft you were flying doesn't use the standard volume datarefs, so you would need to manually adjust the sliders via the settings.

The volume sliders, microphone device, output device, realistic radio checkbox, vhf equalizer options are (now) all saved automatically when changed.

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
3 hours ago, Richard Asberg said:

Another issue, just got this:

1540915097_Greenshot2020-07-0111_24_06-xPilot-RYR888.jpg.2f2c853dbc4c4d1c10500ebadb8891e2.jpg

And here is the full message if of any use to you. This happened after I restarted xPilot and reconnected to the network when X-Plane was already running. Not sure if that was the trigger...?

*snip*

Thanks... I think I found the cause for this problem. It will be fixed in a future release.

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Kevin Townsend
Posted
Posted

OK Thanks Justin, good to know...
Looking again it isn't Drive E it is F, so I guess this means "File"?

I'm still only seeing Vatsim users in Generic liveries, I include the xPilot settings in the 2nd image, maybe you have a suggestion as to where I'm going wrong.
Thanks for your help Justin...



 

xPilot2.png

xPilot3.png

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Richard Asberg
Posted
Posted
54 minutes ago, Justin Shannon said:

The volume slider value is read from the sim/cockpit2/radios/actuators/audio_volume_com1/com2 datarefs. If the volume knobs in the aircraft were initially turned down (set to zero), then that is why the sliders were set to 0. It's also possible that the aircraft you were flying doesn't use the standard volume datarefs, so you would need to manually adjust the sliders via the settings.

The volume sliders, microphone device, output device, realistic radio checkbox, vhf equalizer options are (now) all saved automatically when changed.

This is so cool Justin :classic_smile:! Just tried it in the Zibo mod and works like a charm 👍

A very small issue I noticed though when playing around with this is how moving the volume buttons from 0 to about 50% in the Zibo mod results in the sliders in xPilot being set to about 13%. Moving the volume buttons in the Zibo to about 75% resulted in about 40% in xPilot. Moving the volume sliders in the Zibo to 100% resulted in 100% also in xPilot.

Going back in the other direction (decreasing the volume), the volume set in the Zibo mod was reflected spot on in xPilot. Turning the volume knobs in the mod to 75% resulted in 75 in xPilot, to 50% same thing etc.

Guess this is more an issue with the mod though? Not sending the correct values when increasing the volume for whatever reason.

As for settings being saved automatically, that too is great! However, maybe you should then remove the OK and Apply buttons? Since it becomes a bit confusing when they are not activated even when you've done changes.

52 minutes ago, Justin Shannon said:

Thanks... I think I found the cause for this problem. It will be fixed in a future release.

OK, great to hear you think you already found the cause for this! So, how severe is this issue and what effect will it have on the operation of xPilot? When I saw this, xPilot seemed to continue work fine after I cleared the error message by pressing the Continue button.

Just want to know if I can rely on using this version of xPilot even if/when I see this error message again. Or if I should rather revert to 1.3.15 until you had time to address it?

Richard Åsberg

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
17 minutes ago, Richard Asberg said:

A very small issue I noticed though when playing around with this is how moving the volume buttons from 0 to about 50% in the Zibo mod results in the sliders in xPilot being set to about 13%. Moving the volume buttons in the Zibo to about 75% resulted in about 40% in xPilot. Moving the volume sliders in the Zibo to 100% resulted in 100% also in xPilot.

Going back in the other direction (decreasing the volume), the volume set in the Zibo mod was reflected spot on in xPilot. Turning the volume knobs in the mod to 75% resulted in 75 in xPilot, to 50% same thing etc.

Guess this is more an issue with the mod though? Not sending the correct values when increasing the volume for whatever reason.

This is actually the expected behavior. From the xPilot docs:

Quote

The volume control uses a logarithmic formula to scale the volume with the dataref value; as a result, the volume sliders will not always match the actual volume knob dataref value in X-Plane.

 

19 minutes ago, Richard Asberg said:

As for settings being saved automatically, that too is great! However, maybe you should then remove the OK and Apply buttons? Since it becomes a bit confusing when they are not activated even when you've done changes.

Thanks for the feedback; I will revisit this. There are still some options in the settings window that utilize the Apply and OK buttons.

 

20 minutes ago, Richard Asberg said:

OK, great to hear you think you already found the cause for this! So, how severe is this issue and what effect will it have on the operation of xPilot? When I saw this, xPilot seemed to continue work fine after I cleared the error message by pressing the Continue button.

Just want to know if I can rely on using this version of xPilot even if/when I see this error message again. Or if I should rather revert to 1.3.15 until you had time to address it?

The error should have no adverse effect on the operation of xPilot. Reverting back to 1.3.15 actually wouldn't fix it either because the same "bad" code is used in that version, too. 

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
1 hour ago, Kevin Townsend said:

OK Thanks Justin, good to know...
Looking again it isn't Drive E it is F, so I guess this means "File"?

I'm still only seeing Vatsim users in Generic liveries, I include the xPilot settings in the 2nd image, maybe you have a suggestion as to where I'm going wrong.
Thanks for your help Justin...

This is typically caused by not having the CSL models properly installed. Can you upload your X-Plane log.txt to a file sharing website, such as Google Drive and link it here?

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Richard Asberg
Posted
Posted
2 minutes ago, Justin Shannon said:

This is actually the expected behavior. From the xPilot docs:

RFFM...sorry for wasting your time 😊

3 minutes ago, Justin Shannon said:

Thanks for the feedback; I will revisit this. There are still some options in the settings window that utilize the Apply and OK buttons.

Got it 👍

38 minutes ago, Justin Shannon said:

The error should have no adverse effect on the operation of xPilot. Reverting back to 1.3.15 actually wouldn't fix it either because the same "bad" code is used in that version, too.

Good to know, thanks Justin!

Richard Åsberg

Link to comment
Share on other sites

patrick oneill
Posted
Posted (edited)

CTD when xPilot is loading V1.3.17

This post will not allow me to post the log.txt file as it only accepts images or pdfs so the full cut and paste is below.

Strangely, xPlane is loading xPilot even though I am not running the xPilot APP. This start only with version.

https://bin.clowd.io/?8648e94210ff1c25#6VsMpgheF9L8DGecGmibrBAQkrdAbN1ARDfGqyTLt958

 

I take it all back. After much more investigating it was another plugin that was causing the crashes but purely coincidental the log file was loading xpilot at time of crash. 

Edited by patrick oneill
Move log to pastebin
Link to comment
Share on other sites

Kevin Townsend
Posted
Posted
On 7/1/2020 at 3:32 PM, Justin Shannon said:

This is typically caused by not having the CSL models properly installed. Can you upload your X-Plane log.txt to a file sharing website, such as Google Drive and link it here?

Thanks Justin

https://drive.google.com/file/d/1TixhX3KGCjd1cRwx4y4KOleHEf0JbM1n/view?usp=sharing

There are many lines like this:
0:03:46.015 xPilot/XPMP2 INFO  XPMPMultiplayer.cpp:212/XPMPLoadCSLPackage: Loading CSL package from C:\X-Plane 11\Resources\plugins\xPilot\Resources\
0:03:46.015 xPilot/XPMP2 WARN  CSLModels.cpp:570/CSLModelsAdd: Duplicate model 'B733 B733:BOE', additional definitions ignored, originally defined in line 4 of C:\X-Plane 11\Resources\plugins\xPilot\Resources\/CSL/BB_Boeing/B733
0:03:46.015 xPilot/XPMP2 INFO  CSLModels.cpp:911/CSLModelsProcessAcFile: Read 138 aircraft (138 x B733) from C:\X-Plane 11\Resources\plugins\xPilot\Resources\/CSL/BB_Boeing/B733/xsb_aircraft.txt
0:03:46.015 xPilot/XPMP2 WARN  CSLModels.cpp:570/CSLModelsAdd: Duplicate model 'B738 B738:BRUWL', additional definitions ignored, originally defined in line 17 of C:\X-Plane 11\Resources\plugins\xPilot\Resources\/CSL/BB_Boeing/B738

 

 

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Richard Asberg
Posted
Posted

Hey Justin, hope you're good!

Quick question about the new semi-transparent notification bar option seen below. Does this also affect VR? Meaning you'll have a notification bar popping up in VR. Or is it just for 2D?

RTFM for once 😉 but wasn't able to find an answer to this question and haven't had time to try it out myself yet.

300958399_Greenshot2020-07-0312_37_34-X-System.jpg.22f210a1929a0ae452fea34bad1301b6.jpg

Richard Åsberg

Link to comment
Share on other sites

Kevin Townsend
Posted
Posted
On 7/1/2020 at 3:32 PM, Justin Shannon said:

This is typically caused by not having the CSL models properly installed. Can you upload your X-Plane log.txt to a file sharing website, such as Google Drive and link it here?

Thanks Justin

https://drive.google.com/file/d/1TixhX3KGCjd1cRwx4y4KOleHEf0JbM1n/view?usp=sharing

Looking at Richards post it looks like I've mixed up the backslash.... Standby!

 

 

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Richard Asberg
Posted
Posted
13 minutes ago, Kevin Townsend said:

Looking at Richards post it looks like I've mixed up the backslash.... Standby!

IIRC, it doesn't matter if you're using slashes or backslashes but Justin will have to correct me if I'm mistaken.

Or...why not use the browse button and it will automatically be filled out correctly for you?

Richard Åsberg

Link to comment
Share on other sites

Kevin Townsend
Posted
Posted (edited)

Thank you Richard.
I think I've tried every permutation.
I believe I read it will only delve 5 levels down, if so, you're ok, I'll try another option...

My Log.txt flags

xPilot/XPMP2 WARN  CSLModels.cpp:570/CSLModelsAdd: Duplicate model 'B733 B733:BOE', additional definitions ignored, originally defined in line 4 of Resources\plugins\xPilot\Resources\CSL/BB_Boeing/B733

Which uses both slash and backslash in the url. This is what caused my concern initially.

It also shows...
0:03:27.108 xPilot/XPMP2 WARN  CSLModels.cpp:570/CSLModelsAdd: Duplicate model 'B733 B733:BOE', additional definitions ignored, originally defined in line 4 of Resources\plugins\xPilot\Resources\CSL/BB_Boeing/B733
0:03:27.108 xPilot/XPMP2 INFO  CSLModels.cpp:911/CSLModelsProcessAcFile: Read 138 aircraft (138 x B733) from Resources\plugins\xPilot\Resources\CSL/BB_Boeing/B733/xsb_aircraft.txt

I wonder if the xSquawkbox files in each aircraft folder are no longer required? (xsb_aircraft.txt)

EDIT: Aaah I wonder if I need to convert these to Obj8 models?
Is there a CSL already converted for download somewhere?

 

 

Edited by Kevin Townsend

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Justin Shannon
Posted
Posted (edited)
11 hours ago, patrick oneill said:

CTD when xPilot is loading V1.3.17

This post will not allow me to post the log.txt file as it only accepts images or pdfs so the full cut and paste is below.

Strangely, xPlane is loading xPilot even though I am not running the xPilot APP. This start only with version.

https://bin.clowd.io/?8648e94210ff1c25#6VsMpgheF9L8DGecGmibrBAQkrdAbN1ARDfGqyTLt958

Hi Patrick,

Open the output/crash_reports folder (inside the main X-Plane folder) and look for a dmp or rpt file from this crash and upload it to a file sharing website like Google Drive and share the link here. 

Edited by Justin Shannon

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Kevin Townsend
Posted
Posted
31 minutes ago, Justin Shannon said:

Kevin,

Can you purge your current Bluebell models and try installing the zipped version instead? https://drive.google.com/open?id=0B8hGoqCV5Z5AcTM4ZWhIX2RZT2M

OK Justin, Done. I'm now seeing the correct liveries against the correct callsign. Thank you...
Many appear to have their tyres submerged, should I do something with the offset?

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
6 minutes ago, Kevin Townsend said:

OK Justin, Done. I'm now seeing the correct liveries against the correct callsign. Thank you...
Many appear to have their tyres submerged, should I do something with the offset?

Did you install the vertical offset files?

  • Thanks 1

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Kevin Townsend
Posted
Posted
13 minutes ago, Justin Shannon said:

Did you install the vertical offset files?

Just completed. Justin many thanks.
This completes a long trial, partial success. It seems I had an early CSL collection in the incorrect format for the latest Vatsim client.
Thanks and best wishes
Kev

  • Like 1

The only time you have too much fuel onboard is when you're on fire!

Link to comment
Share on other sites

Richard Asberg
Posted
Posted

Good to hear! 

  • Thanks 1

Richard Åsberg

Link to comment
Share on other sites

  • Justin Shannon locked and unpinned this topic
Guest
This topic is now closed to further replies.
 Share