Touchable main screen.
-
It is nonsense.
Mouse and VGA are absolutely different. if you change your mouse, you have to download a driver from nVidia or AMD?
About FPS….Touch overlay is sending a up to 4 or more finger position data through USB. When you use hotas it hit FPS?
Commercial usage…When peoples start to play video game with PC, who shout a computer is only for business and research.Of course a few person have Big LCD and same size touch overlay. Of course it is no top priority.
But I am hoping and then just saying at all.If you are knowledgable on this issue (was that a proper phrase??), then feel free to contact the devs and offer to do this bit of the sim for them. I’m sure a lot of people would appreciate a touchable main screen!
Personally, this would return to the issue of a “moving target” and I would personally prefer my static touchscreen setup. But good luck!
-
if your vga drivers get fubared on the mouse section you will not have mouse, example jumping pointer, and it’s logical. The mouse drivers just controls the mouse device and where it is, status etc. then reports directly to vga driver where the damn pointer is and the status. Even if the pointer is not displayed the vga knows where the damn thing is so when you move it it displays where it should.
I think it is story of DOS age. I googled and not found. Please give me a reference.
About fps let me tell you that trackir which is an input device (advanced 3d mouse) has fps impact.
TrackIR censor is camera not positioning device. It sends images and TrackIR S/W process images and extract 3 dots and get 6DOF.
Edit oh about the mouse and VGA I talk to you as I have personally first witnessed it and couldn’t believe it also… but had both driver and hw problem.
First driver… then my hw vga died, a slow death… artifacts and so on…You and I will get slow death finally. Who is murderer.
-
No, maybe not. But that dude has 4 monitors and AFAIK, the GPU also renders the left and right side of that touchscreen… it’ll be like having SIX monitors although the bottom left and bottom right are “not displayed.”
The monitor layout in the video of youtube is unique.
I don’t know how DCS support virtual desktop.
And then I don’t have confidence you are right or not. -
You and I will get slow death finally. Who is murderer.
Me not, I hope you neither, but for sure time is for both.
Well the Dos you mention is winxp. There are many still with it.
sent from my Xperia Z3 compact via TapaTalk
-
I have programmed with OpenGL. But i cant understand. Please explain how the mouse works.
DCS supports touching in main screen.
DCS can export screens similar to default BMS screen extraction, with lua scripts modifying (search dcs-eagle forum) , but it is not the case above.
1. There is nothing so complex here. It is just DCS A-10 ordinary 6 monitor output field setup with missing monitors 4&6., and touchscreen as serving monitor no.5.
Basically every “game” with clickable pit would work with this setup. (it should, don’t take my word for granted )2. Touchscreen mouse emulation doesn’t have to be cpu intensive at all., unlike mouse emulation in TrackIr, Freetrack, … where in those you have 3D calculation of an object
(tracker) and (v)syncing with vga output … of course it is cpu/gpu intensive why shouldn’t bein physically connected touchscreen to PC , it is not like this , you just send pressed X,Y coords (or multi X1,Y1, X2,Y2 …with multitouch) and translate them to your liking , mouse,hid etc…
as always depends on setup- it even depends how do you setup touch to emulate mouse.
As usb/ps2 mouse emulation B. As hid-usb (dx) device (like hotas cougar) or … C. as multitouch device (newer, i think requires win7 minimum, but it defaults to HID)
It all depends of type of touchscreen and driver , today even with win7 they should work out of the box
In F4AF my (now dead) 3Mmicro 19" capacitive single-touch worked just fine as second monitor via Touchbuddy , with “ordinary” mouse emulation (no HID) on winXP
It even worked in main screen as seen in that setup above , with 2D and later with 3D pit and + touchbuddy (local server - client) + freetrack,
on my x86 P4 3,2Ghz 3GB ddr1 400 ram , with AGP ATI 2600xt 512mb dd3 ram/… winXPsp3, old configuration, not for BMS, but F4 AlliedForce worked flawless !5. Just to make sure , dont think in the box, today’s android wifi server clients are not the same thing as physically connected touchscreens in windows
Most of touchscreens are usb connected , I’ve had even serial (db9 com) one, so they are basically HID-devices, more similar to usb-joysticks, gamepads, mouse,
then PS/2 keyboard/mouseBut in the end, Arty was more then partially right, … everything depends on type of hw/driver/sw solution, even quality of setup , so , everything is possible, it is just how the concept of approach to the whole thing.
Cheers
- it even depends how do you setup touch to emulate mouse.
-
DCS can export screens similar to default BMS screen extraction, with lua scripts modifying (search dcs-eagle forum) , but it is not the case above.
1. There is nothing so complex here. It is just DCS A-10 ordinary 6 monitor output field setup with missing monitors 4&6., and touchscreen as serving monitor no.5.
Basically every “game” with clickable pit would work with this setup. (it should, don’t take my word for granted )2. Touchscreen mouse emulation doesn’t have to be cpu intensive at all., unlike mouse emulation in TrackIr, Freetrack, … where in those you have 3D calculation of an object
(tracker) and (v)syncing with vga output … of course it is cpu/gpu intensive why shouldn’t bein physically connected touchscreen to PC , it is not like this , you just send pressed X,Y coords (or multi X1,Y1, X2,Y2 …with multitouch) and translate them to your liking , mouse,hid etc…
as always depends on setup- it even depends how do you setup touch to emulate mouse.
As usb/ps2 mouse emulation B. As hid-usb (dx) device (like hotas cougar) or … C. as multitouch device (newer, i think requires win7 minimum, but it defaults to HID)
It all depends of type of touchscreen and driver , today even with win7 they should work out of the box
In F4AF my (now dead) 3Mmicro 19" capacitive single-touch worked just fine as second monitor via Touchbuddy , with “ordinary” mouse emulation (no HID) on winXP
It even worked in main screen as seen in that setup above , with 2D and later with 3D pit and + touchbuddy (local server - client) + freetrack,
on my x86 P4 3,2Ghz 3GB ddr1 400 ram , with AGP ATI 2600xt 512mb dd3 ram/… winXPsp3, old configuration, not for BMS, but F4 AlliedForce worked flawless !5. Just to make sure , dont think in the box, today’s android wifi server clients are not the same thing as physically connected touchscreens in windows
Most of touchscreens are usb connected , I’ve had even serial (db9 com) one, so they are basically HID-devices, more similar to usb-joysticks, gamepads, mouse,
then PS/2 keyboard/mouseBut in the end, Arty was more then partially right, … everything depends on type of hw/driver/sw solution, even quality of setup , so , everything is possible, it is just how the concept of approach to the whole thing.
Cheers
I did read your old post. But you changed context. Why you deleted old post?
Anyway, I am disagree with your new post.
I am thinking mouse pointing/touching mechanism/emulation is not important at all.
Your Mouse thanks for his 2$ or 3$ MCU. That 's enough. No need Intel i7 or AMD Athlon.More then this…
I am agree with your old post about hitting ‘moving target’.
That is point of view about Human Interaction or favor.
I think this would be very critical issue.But I think touchable main screen is ‘ONE PLUS ONE’ gift not ‘Survival of the fittest’ law.
Persons who have 1 big monitor and 1 small touch screen can use Helios way.
The others who have 1 big touch screen monitor can use touchable main screen way.Thanks for your opinion and explains.
- it even depends how do you setup touch to emulate mouse.
-
I am thinking mouse pointing/touching mechanism/emulation is not important at all.
Your Mouse thanks for his 2$ or 3$ MCU. That 's enough. No need Intel i7 or AMD Athlon.Oh, yes it is important, but not in the way you think, performance wise… As I’ve said there is no problem with performance with physically connected devices.
At least there shouldn’t be if everything is correctly connected and operative.But! , Let say you have built small cockpit using 2 screens and one is your touch-screen , now, you don’t just use main screen when you have at least setup like that.
You want some type of screen export function for various export screens, left mfd, right mfd, DED input panel … etc … for all plane functional buttons you want to emulate via touch screen.
Because of that you can’t be in fullscreen mode (like the guy in DCS A-10 , or F4AF), you need windowed mode for BMS.We are talking about 5+ exported windows from the main program (performance impact here too, but not relevant for now, it is still bearable).
Now what is happening . You are working with multiple windows of several, at least two, different applications , cause we aren’t just using ordinary clickable cockpit , again as that guy in DCS-A-10.
We have simulator window , main , and exported mfd’s etc… And we have touch software with our template screens , buttons , like Helios or on android devices.And we are basically pressing buttons with emulated mouse (touch-screen) on that other program (helios/android) so it can translate inputs to keyboard shortcuts or whatever and send it to BMS simulator window/engine.
Now , when you press button on Helios , you’re basically “STEALING” window (screen) focus out of BMS (you loose active window focus, even sound) with emulated mouse on touch screen to the Helios , (like clicking between two or more windows apps in windows)
so it can translate your touch-screen input to key-shortcut and send it to BMS which (at least) should have window focus again to receive that key shortcuts from Helios.Windows are not build that way that you can have 2 or more active (in focus) window applications screens at the same time. One have to be background.
(can’t receive mouse clicks in background)
Simple , No … Easy , YesTouch(mouse) -> Helios -> BMS … or/and … Touch(mouse) -> BMS (clickable pit)
It is not great performance hit for today’s pc (depends on hw/sw), but , few other things can go wrong in this sausage …
Now our emulated mouse comes into play. If we are emulating ordinary mouse then , I’m not sure it will work “normally” , even at all.
(there are workarounds even for ordinary mouse , like return to the main screen after touch event to regain window focus … etc…, that’s too technical for this scope, but not hard )Or, we are using HID-device (DirecX-input) emulation for our mouse, which will our live easier , because DirectX can coexist within several compatible applications at the same time.
Every application which we want will receive that input regardless is it active or in background window.So that’s the catch with type of emulation , not because of performance (chip type quality or whatever)… but as I’ve said , today’s touch screens just because of multi touch capabilities
are default HID-(dx)devices , you can’t have two or more mouse pointers, but you can have XXX mousesCheers
-
I’m getting slightly lost in the exchange, but here are two points:
1. Helios will work with BMS even if BMS is in fullscreen mode.
2. If having a “touchable main screen” is so easy, how can we do it in BMS?The reason I’m saying it can’t be done in BMS is because this issue came up a few years ago IIRC and one of the devs confirmed it wasn’t possible.
-
Oh, yes it is important
EMULATION is mean of ‘YOU CAN FORGET’. If you cannot forget? It is not emulation.
So Touch screen is just mouse. and you have to forget Touch screen.
All emulation have just one problem….Performance.
But, as you know, touch/mouse emulation eats no CPU or very very bit.I am a programer. As i know, mouse system have 3 basic events.
MouseMove, MouseUp, MouseDown. All platform would be same or have small difference.It is simple. NO TOUCH JUST MOUSE.
You can use Helios with a mouse now. so you will can use Helios with the big flat mouse too.
Thanks.
-
I’m getting slightly lost in the exchange, but here are two points:
1. Helios will work with BMS even if BMS is in fullscreen mode.
2. If having a “touchable main screen” is so easy, how can we do it in BMS?The reason I’m saying it can’t be done in BMS is because this issue came up a few years ago IIRC and one of the devs confirmed it wasn’t possible.
Well , 1, for the fullscreen … I guess in that kind of setup , BMS is not using touch screen for display, right, ? It is only displayed fullscreen on the main monitor.
(there are workarounds even for ordinary mouse , like return to the main screen after touch event to regain window focus … etc…, that’s too technical for this scope, but not hard )
When using touchscreens, we know target application exe name in memory, even process ID. , So we can activate focus of any window from touch-application., especially of
that which we want to, trickFrom the touchbudy.cfg (similar tricks are used probably im Helios)
#=====================
Some games prevent the mouse cursor from leaving the game window area.
Enabling this option allows TouchBuddy to try to release the cursor
(Note: This option does not work on all games!)
clip_cursor = 1
this is another way to try to unlock the game mouse, but it does cause a
LOT of problems. I highly recommend you do not use this unless you
absolutely have to!!
release_capture = 0
#=====================
In Local mode, when you press on the TouchBuddy window, the mouse/cursor
will move to the area of the button, but after pressing the button, the
cursor will stay there. By defining the following value, TouchBuddy will
move the mouse/cursor to the defined position after a button press.
If its defined as “centre”, the mouse/cursor will be moved to the centre
of the currently active window.
If its defined as “previous”, the mouse-cursor will be moved to where
TouchBuddy saw it last time round its 1 second timer loop (this option works
remarkably well from my limited testing!)
#mouse_position_after_press = 320,240
#mouse_position_after_press = 800,600or
#mouse_position_after_press = centre
or
mouse_position_after_press = previous
Try to understand this config. Everything will be clear.
2. Well, how is tough question, there are so many types of setups… You people wouldn’t believe.
There isnt ‘easy’ answer on this, depends on your configuration, mostly, and what you want to achieve.Cheers