Just second mission in mission list and first flight.
I restarted new campaign and then, callsign is same and AWACS reply well.
Just second mission in mission list and first flight.
I restarted new campaign and then, callsign is same and AWACS reply well.
I requested AWACS Picture & Declare, but all commands were ignored.
In briefing document, AWACS callsign was ‘Sentry1’. But when i requested AWACS command, radio voice spoke ‘Chalice1’.
Is it bug?
The BE must be stored in the dtc file. Its an ini file. Not 100% sure . But there r the waypoints so BE must be also among other. BE is waypoint 25 iirc.
sent from my mi5 using Tapatalk
Thanks. But there is no BullsEye in *.ini file.
When i saved campaigns as name T1 & T2 with Time stoped, nothing changed except Bullseye (only changed),
Other files(*.twx, *.frc, *.his, *.ini) is same, only T1.cam is different from T2.cam.
it is wrong forum.
how to delete this?
I can get x, y position from falcon BMS’s shared memory with JAVA.
How many feet is the left / bottom of the knee map?
How to get the location of bullseye from saved campaign files?
I tried to figure the position in file with saved files which just bullseye was changed.
I had expect 8 byte. But many byte were diffrent from each other.
I tried with old falcon source code. but i did not even understand what is GridIndex.
I can get x, y position from falcon BMS’s shared memory with JAVA.
How many feet is the left / bottom of the knee map?
How to get the location of bullseye from saved campaign files?
I tried to figure the position in file with saved files which just bullseye was changed.
I had expect 8 byte. But many byte were diffrent from each other.
I tried with old falcon source code. but i did not even understand what is GridIndex.
When package has two or more flight, tag is omitted at end of own flight.
so below tables are handled as children s.
In addition,
About weather section, no need to add option width=“50%”. it forces truncate lines with small screen like tablets.
About CSS, no need to reduce line-height to 80%. Some html viewer shows lines as overlayed. 100% is ok.
Thanks.
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.
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 boxIn 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.