Linux64 bit support
-
- Posts: 9939
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: Linux64 bit support
Wow, that is quite a find, thanks so much for tracking that down. I'll check that area of the code to see what's going on. It's platform specific so this'll be interesting.
-
- Posts: 9939
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: Linux64 bit support
Is there anyone who was having crashes with the 64-bit plugin on connection that is STILL having a problem while using the shortened callsign?
-
- Posts: 56
- Joined: Mon Feb 25, 2013 9:58 am
Re: Linux64 bit support
Just tested my setup. I'm able to connect with the abbreviated tail number . Disconnecting from PE yields a crash to desktop that I haven't ran GDB on yet. That might have something to do with my particular setup, especially since I'm not able to broadcast. Tried testing recording in Audacity using my USB headset, and Audacity is not happy either. Looks like I've got some work to do on my end, so don't consider my experience to be typical.
Re: Linux64 bit support
Just my $.02.theluckyone17 wrote:Just tested my setup. I'm able to connect with the abbreviated tail number . Disconnecting from PE yields a crash to desktop that I haven't ran GDB on yet. That might have something to do with my particular setup, especially since I'm not able to broadcast. Tried testing recording in Audacity using my USB headset, and Audacity is not happy either. Looks like I've got some work to do on my end, so don't consider my experience to be typical.
No crashes to date, while flying or disconnecting. No issue with Logitech G330 USB headset.
Ubuntu 14.04 LTS 64 bit
XP10.25
Re: Linux64 bit support
The plug in does NOT work unless a physical button is mapped to "contact ATC". Please see:Keith Smith wrote:Is there anyone who was having crashes with the 64-bit plugin on connection that is STILL having a problem while using the shortened callsign?
viewtopic.php?f=12&t=4511
FWIIW, I have completed a half dozen flights using the Unbuntu 64 bit/PE combination with no significant issues. I did have a PE disconnect on a VERY long flight but was able to re-connect. The controller stopped monitoring me which created an "issue" when at TOD. However, I can't say this had anything to do with Linux.
However, I have noted an odd difference between Windows and Linux. On Windows the BE58 starts out with the parking brake set and engines running. Under Linux the initial ramp start does NOT set the parking brake. Therefore when changing position the 1st thing one must do is set the parking brake.
I'm also assuming that there are still unresolved issues with the 32 bit Linux/PE version as previously documented. Yea I know. Fixing issues with the 32 bit version isn't a priority. Especially if the 64 bit version is working.
-
- Posts: 56
- Joined: Mon Feb 25, 2013 9:58 am
Re: Linux64 bit support
Woohoo! Figured out my recording/headset issues. Playback was fine, but recording was a no-go. Kept getting a "cannot submit urb 0, error -28: not enough bandwidth" error in dmesg just after plugging in my USB headset (Plantronics Gamecom 780). PAVUControl failed to display the recording volume as well. Turns out that I needed to enable CONFIG_USB_EHCI_TT_NEWSCHED in the kernel. Simple fix, but it was a bit hard to track down.
Connected to PE using a five character tail number. KVNY Ground gave a five by five on a radio check. Didn't actually get any flight time in, due to the late hour here on the east coast. I did get a CTD when disconnecting from PE:
I'll confess to not being horribly concerned. It should only affect preferences being saved. I can resolve that by setting my preferences and restarting before starting PE. I will have to remember to end my flight in FSEconomy before disconnecting as well, but I try to make a habit out of that anyway. It'd be nice to get it resolved, but with a workaround available, it get solved when it gets solved. Life is good!
Connected to PE using a five character tail number. KVNY Ground gave a five by five on a radio check. Didn't actually get any flight time in, due to the late hour here on the east coast. I did get a CTD when disconnecting from PE:
Code: Select all
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6ea363b in pthread_join () from /lib64/libpthread.so.0
(gdb) bt
#0 0x00007ffff6ea363b in pthread_join () from /lib64/libpthread.so.0
#1 0x00007fffb1f183af in pt::thread::waitfor() ()
from /home/noel/X-Plane 10/Resources/plugins/PilotEdge/64/lin.xpl
#2 0x00007fffb1ee44e7 in VSProClient::disconnect() ()
from /home/noel/X-Plane 10/Resources/plugins/PilotEdge/64/lin.xpl
#3 0x00007fffb1edabea in disconnect(int) ()
from /home/noel/X-Plane 10/Resources/plugins/PilotEdge/64/lin.xpl
#4 0x00007fffb33cb335 in XPLMHandleMenuItemPick(int) ()
from /home/noel/X-Plane 10/Resources/plugins/XPLM_64.so
#5 0x00007fffb33c40d2 in XPLMMenuHook ()
from /home/noel/X-Plane 10/Resources/plugins/XPLM_64.so
#6 0x0000000000c13478 in XPPHandleMenu(int) ()
#7 0x0000000000961f90 in mbar_class::mbar_select_an_item() ()
#8 0x00000000009627f8 in mbar_class::mbar_select_an_item_click() ()
#9 0x00000000006a2efa in MACIBM_handle_click(int) ()
#10 0x0000000000e6f6c8 in LIN_handleevt(_XEvent*) ()
#11 0x0000000000e6dad0 in WIN_event_loop(int) ()
#12 0x0000000000e6dc09 in WIN_run_app ()
#13 0x00000000011467bc in main ()