Cannot move tablet around
-
For those using LEGACY below follows an example on how to setup a button to switch between two tablet positions using Spad.Next
Custom Tablet Position
Spad.Next button pressed example (you only need to use the LVAR highlighted in the red box
Coordinates to the Tablet default position
-
Fantastic! Thank you for sharing this! I might also add that setting the L:Var_efb_dist can also be used to override my automatic distance limitations that keep the tablet from being too close the camera, or clipping thought the walls. This might be useful if you're looking to set a really custom position, such as in VR.
-
Interesting approaches to help! SpadNext is a great software, but sorry, not everyone has it or needs it.
This is my problem:
I can open the Duke-tablet with the mouse, but I can't move it with the mouse, neither in "Legany" position nor in "Lock" position, also the top frame doesn't turn blue.
Btw, if I select "Lock" all mouse operations are non-functional.
Yes, I can open the pop-out tablet window with the right ALT key and mouse, then I can also move this window. If I now close the original tablet window, no more data is transferred in the pop-out tablet window. (I don't need two identical tablets)
I don't have this problem with the A2A Comanche tablet.
Win10 - MSFS PC - DX11- MSFS SU14 Premium Deluxe Edition -
I too can move the tablet around freely (in Lock mode only) but am unable to select any of the options/tabs.
-
@foxtrot789 said in Cannot move tablet around:
I too can move the tablet around freely (in Lock mode only) but am unable to select any of the options/tabs.
I have exactly the same problem and I have tried in SU14 DX11 and SU14 DX12, no change. Lock mode allows me to move the tablet but none of the buttons on the tablet are clickable. I can make the buttons on the tablet "react" by right-clicking on them, but it does not actually click.
-
I got an email from tech support today that they had solved several interaction problems by discovering that some users had the infamous Horizon 787 installed, which overwrote core simulator files pertaining to interactions. They were also able to solve a few other tablet related problems, so please reach out to them if you continue to have problems.
-
Thank you for the help, I was able to figure out how to move the tablet (in the Accessibility Settings) although I still have no ability to select any options or navigate the different tabs. I'll double check I dont have the previously mentioned 787 files that may be the issue.
FWIW, I did do a repair install and that didnt fix it.
Thank you very much for your amazing dedication to helping us dummies.🙂
-Trevor
-
Hi All,
I just wanted to let you know that I fixed the dragging in legacy mode. It was actually a lot easier than I expected, which is nice for a change. It will be in the next update, which I can hopefully get to you all shortly. Thank you, and happy flying!
-
@Black-Square Thank you! Do you think this will allow us to also use the tabs and functions?
At the moment a fair few of us are reporting tablet is not usable regardless of accessibility mode and 787 presence. Buttons show but they are not clickable. I can get them to “react” by right-clicking (ie a white square animation will appear) - but it does not result in an action.
Many thanks
-
Unfortunately, I have been unable to determine what the cause of this could be. It has nothing to do with legacy interaction mode, to the best I can tell. I will be talking to Just Flight support this week to see what they have learned on the subject, but I am currently operating under the assumption that this is a user-end problem, because I have yet to find any setting in the simulator that could cause the tablet interactions to stop working. The tablet touch screen should be no different than any other touchscreen in the cockpit, for reference.
I'm sure that's not the answer you were hoping for, and I'm very upset that some of my users have been unable to enjoy the tablet so far. I will let you know if I hear anything. In the meantime, I'm happy to help anyone troubleshoot here. I have one new idea that someone could try:
Try popping the tablet screen out to a window by clicking on the screen while holding RIGHT-ALT. All of the interactions should work in pop-out mode too. If they don't, then we've learned the problem lies within the tablet's software (possibly an installation issue), rather than the simulator's interaction functions.
-
@Black-Square Interestingly, popping the screen out does not work. MSFS doesn’t see it as “poppable” and the magnifying glass icon does not appear when you hover over the screen.
This is the only tablet I have issues with (I have a collection of add-ons with tablets which are working well inc. but not limited to Fenix A320 and PMDG737).
Don’t know if it helps in any way but in legacy interaction mode I can’t do anything, not even move the tablet, or make the buttons “react”. In “locked” mode, I can move the tablet and make the buttons “react” but they don’t do anything.
I have now updated to SU15 so will uninstall then reinstall the Dukes using the SU15 option during installation, try again then report back.
-
@JPChabert said in Cannot move tablet around:
I have now updated to SU15 so will uninstall then reinstall the Dukes using the SU15 option during installation, try again then report back.
Done and unfortunately hasn't fixed the issue.
I have uploaded video of the issue here. Ignore the sound (not relevant to issue).
EDIT: Now fixed. All I did was uninstall the Horizon-sim B787 as I read it may have odd interactions with the sim.
-
Are there any other (known) files that could effect the tablet not working properly? I don't have the 787 files in my community folder but when I moved everything out of the folder and ran the sim again, the tablet worked fine...
Or, does anyone know the specific 787 file name that causes problems so I could do a search for that file (maybe it's hidden in a non-787 folder.
Thanks for the help!
EDIT: Got it working... These were my findings for anyone else out there that this might help:
Likely the first fix was that I found more 787 files that windows search failed to find...
Additionally, these new found 787 files were not in a "horizonsim-aircraft-787-9" folder, but rather a file folder titled "B78XH-main".
Once I got rid of this "B78XH-main" folder, I ran the sim and the Turbine Duke was all sorts of screwed up. So I uninstalled, and re-installed and it's working as it should, tablet and all.
Hope this helps.
-
The var_efb_dist seems to be limited to how far forward it can be set? In VR it needs to go much further forward than 2D, but it seems to be constrained. Is there a way around this?
-
Here is what I did to create a better tablet solution for VR users in the next update. I will continue to think about how I could create an even more versatile tablet movement system in the future.
-
@Black-Square when will the update be available that includes that option?
