skypickle

what do you folks like for potentiometers? With the numerous dials and sliders in an aircraftfor lights, I need to build something. Since radio shack closed, I have no easy access to hardware and have to order online. What electrical specifications are required? Which pots have the smoothest and damped feel?

I just noticed you use the variables, padding and offsetX , but I neglected to add them because I was focussed on the ' highliughted lines' I saw early in this thread. When I included the entire fix in your post from Friday at 9:47, it works. Please forgive my sloppiness. This is what I now see

This solution does not work with the following monitor config: monitor config --4096 x 3240 4096 screen with a 1920 screen below it _ = function(p) return p; end; name = _('Camera + 2 MFCDsLG'); Description = '2 MFCDs on the bottom and camera on the top' Viewports = { Center = { x = 0; y = 0; width = 4096; height = 2160; viewDx = 0; viewDy = 0; aspect = 4096 / 2160; } } LEFT_MFCD = { x = 20; y = 2160 + 240; width = 810; height = 810; } RIGHT_MFCD = { x = 1080; y = 2160 + 240; width = 810; height = 810; } GUI = { x = 0; y = 0; width = 4096; height = 2160; } UIMainView = GUI GU_MAIN_VIEWPORT = Viewports.Center The 'george' window is offscreen somewhere. Please note that monitor one which is off to the left is for browsing pdf files , websites and other flight instructions, etc while in DCS which plays on monitor 2 The MFDs properly render A10 MFDs.

When all monitors are lined up, the location (0,0) is at the top left. So for example in this array monitor 1: 3840 x 1600 monitor 2: 4096 x 2160 monitor 3: 1920 x 1080 So to use monitor 2 as the DCS game window I specify monitor config to be _ = function(p) return p; end; name = _('Camera + 2 MFCDsLG-Hh'); Description = '2 MFCDs on the bottom and camera on the top' Viewports = { Center = { x = 3840; y = 0; width = 4096; height = 2160; viewDx = 0; viewDy = 0; aspect = 4096 / 2160; } } LEFT_MFCD = { x = 3840 + 4096+20; y = 1080 + 240; width = 810; height = 810; } RIGHT_MFCD = { x = 3840 + 4096 + 1080; y = 1080 + 240; width = 810; height = 810; } GUI = { x = 3840; y = 0; width = 4096; height = 2160; } UIMainView = GUI GU_MAIN_VIEWPORT = Viewports.Center but this gives me the weird result on monitor 2:And when DCS is in focus, monitor 1 is black - I cannot read any browser I might have pulled up there. However when I specify this display config: I can start counting my monitor config from the top left of monitor 2 and this config file: _ = function(p) return p; end; name = _('Camera + 2 MFCDsLG'); Description = '2 MFCDs on the bottom and camera on the top' Viewports = { Center = { x = 0; y = 0; width = 4096; height = 2160; viewDx = 0; viewDy = 0; aspect = 4096 / 2160; } } LEFT_MFCD = { x = 20; y = 2160 + 240; width = 810; height = 810; } RIGHT_MFCD = { x = 1080; y = 2160 + 240; width = 810; height = 810; } GUI = { x = 0; y = 0; width = 4096; height = 2160; } UIMainView = GUI GU_MAIN_VIEWPORT = Viewports.Center I get the main DCS game window on monitor 2 and the MFDs on monitor 3. The number of pixels rendered in this arrangement is 4096 x 3420=14,008,320 So it seems DCS sets (0,0) to the corner of the largest monitor. I realize I could shift monitor 3 all the way to the right in the display settings then I could make a monitor config with fewer total pixels for 2 and 3. (4096 +1920 x 2160 = 12,994,560) But that would confound me having to move my mouse to the right to get to monitor 1 when it is physically located to the left.

@Jayhawk1971 you mean to tell me casmo made two videos about acquisition sources?

i think i understand now why there is even the architecture of sight and acq. Because there are two people in the aircraft. Each person has his own eyepiece,and his own MFDs. Each person also has access to weapons. However there is only one pnvis and one TADS. So the first generation of this system probably was a way for the either the pilot or cpg to share these devices which became labeled acquisition sources. Because each person has his own eyepiece, his own the ability to store his own 'mark points' , and use his own MFDs, a way was needed to give that person a label for the function that could serve this info yet be able to couple to a location on the ground derived from either the TADS(which is shared) or his stored mark points or just use the location of his head. Somewhere in the evolution of this system, someone imagined that using the location of the person's gaze (as measured by his head position) could also be a useful piece of information. So head position was added to TADS as an 'acquisition source'. FCR will provide yet another way to get ground location data. Linked battle space data will be another acquisition source ( I think this was added to the AH-64E) In summary I would define an acquisition source as any gizmo that provides ground location data. I would define 'sight' as any gizmo that passes that info to the pilot and the weapon he has selected. So a sight would be the eyepiece thingy with its weapons interface or an MFD showing the TSD or the TEDAC.

I thank you all for the chorus of help.

Casmo's video: I am probably wrong but have labeled some of the parts. Could someone confirm my identification of parts?

@AvroLanc thank for trying to explain what seems to be a confusing topic. Most of the videos use these words differently. You stated: "If you removed the ACQ SOURCE concept from the whole helicopter, you could still go out and shoot up targets all day long with your 3 SIGHTS (HMD/TADS/FCR), just like the Hind or a fancy Huey. BUT….it’ll be much harder to know where to look, and more time consuming and extra effort to search and point with those 3 SIGHTS. " Typically, in the A10, the sights we use have 'their own 'brains'. The TGP can 'remember what it locked on to. And it can be locked onto what it sees or the current waypoint. The maverick can remember what it locked on to independently. The TAD can show me the SPI as well as data from the link and all the other aircraft in my net. The HMCS can show me the TGP video, where the TGP is looking, the SPI, as well as data from the link from other aircraft. I can point my weapon to a SPI generated with TADS , HMCS, TGP Your comment: 'the confusion is that a SIGHT can also be an ACQ source. ' is right on. Perhaps I need to make a list of three columns: 1st column - display device ( and how it is selected). These are the articulated borg-like thing on the pilot's helmet next to the eyeball, the same thing that is in front of the CPG eyeball, the TEDAC, the MFDs 2nd column - sight (and how it is selected and manipulated - moved, zoomed, to which acquisition sources can it be 'slaved' to extract position data), The sights I can use are an MFD showing the TSD, an MFD showing video, the TEDAC. 3rd column - acquisition source (and how it is moved, zoomed as well as where its data can be saved). Pushing the ACQ button on the MFD gives me a list of acquisition sources When I do this, then I start to see many combinations that can exist but dont make sense Conceivably I could make a chain like this pilot eyeball-> pilot'shelmet sight ->gunner sight -> TADS.. So what's the acquisition source in that example? or CPG eyeball -> CPG helmet sight -> Pilot helmet sight -> TADS -> waypoint? add PNVIS, FCR in there and the soup gets murkier. And where does the TEDAC fit in? is it just a display or does it have it's own sighting system? Somewhere I read that the TEDAC has its own computer and sighting with the TEDAC is better than with the helmet. @PlainSight when you press 'slave' what are you slaving to?always the acquisition source? If that's the case, what are you slaving to the acquisition source- the display next to your eyeball, the TEDAC, the PNVIS, the video on the MFD? How do you pick 1)what you are slaving and 2)what you are slaving it to

I watched this and read the manual. Initially I thought an acquisition source was the gadget used to find the target. But then I read in the The manual, 'the cued line of sight reticle indicates the location of the selected acquisition source'. So an acquisition source is a location? Why dont they just say target? I know there are different ways to get the location of the target-for example, it could be the TADS, it could be the cursor (CAQ button), it could be fixed, it could be the pilot's helmet sight (if you are the CPG), it could be the gunner's helmet sight (if you are the pilot) or it could the cryptic tech labeled '7skr' or '?00'. So that's why I thought the acquisition source was the gadget identifying the target. But the confusion arises because they say the acquisition source can be the pilot's or CPG's sight. So is an acquisition source really just a sight? And when I used the sight select switch (HMD,TADS, FCR) am I not just designating which tool I am using to identify the target? Can someone clearly and simply explain why there is an 'extra layer' in between me and the target? Why isn't the sight select switch enough? In the A10 we have SOI (which is the tech used to 'sight' the target) and SPI (the actual target in the sight). If the acquisition source is like a SPI, then it should be a location (as the quote I pulled from the manual indicates). But then why should there be a button on the MFD that allows me to set the acquisition source to a tool ( a sight) when it is a location?

@Avenger31 Unfortunately I do not have the F16. But if I fly the huey first, it makes no difference. even with this line added to the lua file (just before the KA-50 statement) like so: elseif obj.Name == "AH-64D_BLK_II" then dataTable.name = "UH-1H" elseif obj.Name == "Ka-50" then or this line: elseif obj.Name == "AH-64D_BLK_II" then dataTable.rpm = string.format("%.2f", 5000) I get this error on quitting DCS.

After shutdown, despite turning off battery and APU, MFDs reain on. Also note throttle settings do not zero.

1) master arm on 2) WASup the gun 3)press B6 on L MFD 4) enter A into keyboard unit, press enter Gun remains in manual fixed range. see attached track Interestingly, the autoranging is reflected in the HMD overlay with the TADS as well as the TEDAC. However, the gun page on the left MFD continues to display manual 3000. AH64dgun2.trk video as well gun.mp4

Thank you for the reply. I guess that's a bug in the MFD display then. I'll report it in the bugs section.

I also tried with the TADS as acquisition source slaved to the gunners helmet. Again, the gun range stays manual. Track attached. AH64dgun2.trk

i think this is purposely done because you cannot see the TEDAC very well as you turn your head. Therefore the TADS must be visible so you can know when to 'deslave' the TADS from the HMD. And the only way you can effectively see the TADS in the HMD is if the aweful green overlay is projected onto your HMD. It would be so much better if the monocle had an OLED panel that could be AR mode (showing both the TV AND the TADS) or with the flick of a button go in VR mode (only showing the TADS). That way I could choose to disable that distarcting overly bright background that is useless in daytime when I am targeting. I guess that will have to wait for the Apache64-E.

1) master arm on 2) WASup the gun 3)press B6 on L MFD 4) enter A into keyboard unit, press enter Gun remains in manual fixed range. see attached track AH64dgun.trk

How did you get it to work? by adding this line to the simshaker lua file? elseif obj.Name == "AH-64D_BLK_II" then dataTable.name = "Mi-24P"

Here's a Huey profile . I got all the radios and most of the buttons and dials. The icons are not the best. And I had trouble figuring out some of the parameters but it mostly worksI confess I did steal on button from another profile for organizational inspiration (the icon of the chopper) and really should delete it. UH1.streamDeckProfile

I can autorotate the huey no problem, but the Apache just wants to dive into the ground. I start level flight at 90- knots , pull back the throttle to . The cyclic has no authority. I decrease colective to keep rotor rpm up but she just noses over just the same. I apply a little collective and she seems to want to get her nose up but the rotor stalls out.

I mean what is the likelihood of both guys being named George? How about some cool names like Hazard and Duke? Then in the controls section you can refer to the 'other' guy with the proper name. The AI slot can remain nameless because it assumes the identity of the either crew.

Interestingly, the update checked off the game avionics button. I did not realize it and when I unchecked it, all the flight instabilities disappearred.

I am getting it in instant action missions. I noticed that game avionics got checked with this update so that must be it.

I had this issue in the instant missions.