Hi Vlad,
Should the current version of SimVimPanel work with SimVimCockpit v0.9.42b? I see that 42b has connection protocol for upcoming new version of SimVimPanel. I am having connection problems and wondered if I need to go back to 42a or wait for the new version of SimVimPanel. Panel is running on a laptop connected to X-Plane computer via WiFi. Instruments appear OK, but do not respond to plane movement.
Regards, Geoff
related to an answer for: New SimVimPanel
in System Issues by

1 Answer

0 votes
Hi Geoff,

The latest changes in the plugin should not affect the current SimVimPanel version.

What system do you use to run SimVimPanel?
Does the plugin's Status window show the established connection?
We've noticed before that, for some reason, on some systems the panel is not updated even if connection is established (noticed it on 1 computer with Linux - 2 other computers with different Linux versions worked fine).

There will be no such issue with the new SimVimPanel version, as it was completely reworked.


Hi Roman,

I'm running the current version of SimVimPanel on an Asus laptop (Windows 7). It is set up to use the Basic Six panel. Have tried connecting via both Wifi and Ethernet without success. I can ping the main computer from the laptop and vice versa, so there is a good network connection. The status window in the plugin never sees the panel connection. Interestingly, the artificial horizon gauge doesn't appear. If I press the "L" key, it then appears, but on release of the "L" key, all gauges disappear and I cannot get them back.

I've reinstalled the Panel software, but no change. Log file contents:

[INFO              ] Logger: Record log in C:\Users\HMAC\.kivy\logs\kivy_19-08-30_15.txt
[INFO              ] Kivy: v1.9.2-dev0
[INFO              ] Python: v2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)]
[INFO              ] Factory: 179 symbols loaded
[INFO              ] Image: Providers: img_tex, img_dds, img_gif, img_sdl2, img_pil (img_ffpyplayer ignored)
[INFO              ] OSC: using <thread> for socket
[INFO              ] Window: Provider: sdl2
[INFO              ] GL: GLEW initialization succeeded
[INFO              ] GL: OpenGL version <3.1.0 - Build>
[INFO              ] GL: OpenGL vendor <Intel>
[INFO              ] GL: OpenGL renderer <Intel(R) HD Graphics Family>
[INFO              ] GL: OpenGL parsed version: 3, 1
[INFO              ] GL: Shading version <1.40  - Intel Build>
[INFO              ] GL: Texture max size <4096>
[INFO              ] GL: Texture max units <16>
[INFO              ] Shader: fragment shader: <No errors.>
[INFO              ] Shader: vertex shader: <No errors.>
[INFO              ] Shader: program: <No errors.>
[INFO              ] Window: auto add sdl2 input provider
[INFO              ] Window: virtual keyboard not allowed, single mode, not docked
[INFO              ] Text: Provider: pil(['text_sdl2'] ignored)
[INFO              ] GL: NPOT texture support is available
[INFO              ] Base: Start application main loop

What have I forgotten to do?