BiPod

OK. I've given this a try a couldn't improve much over what we have already got. I can't tilt the head the way I want. Maybe someone else can come up with something, but I am going to let the matter rest for now. Mildly improved explanation of parameters: (originally from BoredTechie) Snap[L][M]["N"]=O L is the plane and 11 is the id for the A10 M is the KEYPAD value + 1, so for example KEYPAD1 would be Snap[11][2], KEYPAD2 Snap[11][3] etc. N is the value you're changing where:- y_trans up(+) and down (-) z_trans right(+) and left (-) x_trans back(+) and forward(-) vAngle pan view ---------------------------------> like a head nod rollAngle look left (-) and look right (+) ---------> Head Roll/tilt viewAngle = field of view / zoom -------------------> Zoom hAngle pan view------------------------------------->like a head shake BiPod.

Yes....and a very popular question it seems to be. RCtrl-NumPad0 will latch the snapviews so you can press any numpad key once and the view will hold, then press another numpad key to go that view. To unlatch press RCtrl-NumPad0 (or just NumPad0) again. OR You can program your HOTAS to do it just as you said. Press a hat key once to go to that view, press once more to return to normal view. I have done this with SST programming of my x52. If you have that stick I can show you how. BiPod.

I'm afraid I couldn't figure out a way either. It would be much better to be able to see the warning panel and electrical panel in the same view, and tacan and lights panel together, but as you pointed out, it seems to be limited. I'll have another look at tilting the head tonight, but I am pretty sure it can't be done, otherwise I would have done it before.:( Please somebody prove me wrong! BiPod. EDIT: P.S. I have edited my post that you linked to in your OP to make my lua edits clearer and easier to use. Thanks again to BoredTechie for some of those angles.

Thanks for the kind words. I think I might give your 7 and 9 a test drive:) You might want to zoom out a bit on the MFCDs, but as long as you can easily click the OSBs then it's OK. As you don't seem to be able to save in game, it looks like lua editing is the only way to go. Cheers, BiPod.

Here is the more advanced version: http://www.youtube.com/watch?v=24o3l1uD7Aw

Wow psychic!

The best I know of is Strongharm's unofficial FPS benchmarking mission: http://forums.eagle.ru/showthread.php?t=66755 He has also done the FPS Killer for those with a supercomputer: http://forums.eagle.ru/showthread.php?t=66723 The missions were built before the final release, but I think they will still be OK. There may also be other relevent threads in that section that I haven't seen. Cheers, BiPod.

" Is me not pushing this the reason why I cannot turn on lights" Yes. WarriorX is also correct. I use Pinkie aft (lights according to panel) before setting my lights. Your anti-collision switch won't hold in positon otherwise. Then just click pinkie centre to turn all exterior lights off when approaching the combat zone. Note that you will have to manually set the anti-collision switch every time after you use the pinkie. BiPod.

I don't use labels myself, but here is a good idea for reducing their visual impact by turning them into a " ` " : http://forums.eagle.ru/showthread.php?t=55121&highlight=labels.lua This is from CombatAce: In the labels.lua file do this. AirFormat = {} AirFormat[10] = "" AirFormat[5000] = "'" AirFormat[10000] = "'" AirFormat[20000] = "'" AirFormat[50000] = "'" GroundFormat = {} GroundFormat[5000] = "`" GroundFormat[10000] = "`" GroundFormat[20000] = "`" NavyFormat = {} NavyFormat[10000] = "`" NavyFormat[20000] = "`" NavyFormat[40000] = "`" WeaponFormat = {} WeaponFormat[5000] = "l" WeaponFormat[10000] = "l" WeaponFormat[30000] = "l" Note: Red color indicates what you need to change. BiPod.

Here you go. I won't sing its praises too highly, the only real thing I did was put in a steep [?z-axis?] response so that you can lean forward a little and get a good MFCD view. Try that, its cool! I've also restricted lateral head turns a bit. I couldn't attach an .xml for some reason so I changed it to .txt. Make sure you change it back to .xml before you use it (just rename the extension bit). I have TIR 4 with version 5 saftware. Cheers, BiPod. DCSA10C.txt

These are the numpad views. Hold Num0 and then another number to temporarily see the view. press RCtrl-Num0 to latch the views without holding them. If you have space on your joystick, I recommend binding them. Celebrating my 100th Post :yay: BiPod.

You definitely aren't! The default will work for every application, but better results are obtained by customising. eg. For blackshark you don't need to look up except to see the sunroof, so I have it "snap" to the sunroof and hold. Also, seeing and clicking the rear right panel was hard for me, so I have the X axis pan slowly to the right across the window and then snap and hold on the rear panel to make it easy to mouseclick and forgiving on my neck. It's a lot of messing around though to get your profile just right, but worth it for me. Cheers, BiPod.

Hi All, There was talk at one stage of being able to save snap views "in game" and with the final release we now have the "Save Cockpit Angles" option (RAlt-Num0), but for the life of me I cannot get this to work, and there seems to be no mention in the manual. I have previously created lua edits as shown below. I think this is what "Save Cockpit Angles" is meant to do. Has anyone got this to work in game without editing lua files? Am I totally wrong about what this is meant to do? I have gone back to my old lua edits for now. The method still works as given by BoredTechie http://forums.eagle.ru/showthread.php?t=62820 If you are interested, these are my edits for the images above, but if someone knows how to save in game that would be great. Cheers, BiPod.

I've had the same problem since Beta 1 and it still persists. The only workaround I have is to set the A-10 profile to "Exclusive" in the TIR software "Profiles" tab. You then have to manually change this everytime you want to run another program such as FSX or Blackshark, but at least you can have a different setup for BS and A10. I have a TIR 4 with 5.1.200 (Build 9414) software on a 64 bit system. The problem existed with earlier software versions and with the 32 bit A-10 software from the Betas. BiPod.

Thanks for the input Bahger:), but I will stand by my statement. I agree, there is no problem at close range such as the overflight example you have given, but at 15-20 miles when you are first aquiring your target it is a different story. In the overflight example, the angles are usually fairly steep, and a lot of belly is being shown. Enjoying the complexity and nuances of this sim, BiPod.

Yes, this is weird, but I assume it is a genuine feature. If the target is a long way away, it will not lock out of the "corner of the eye", even if the image is clearly visible. I used to turn the nose towards the target like you do, but have found that you can lock by just showing the target your belly. ie. If the target is off your right wing and won't lock, bank hard left while flying straight and it should lock easily. This is for the TGP only. The short range and slow seeker head of the Mavs makes this method unsuitable for them (maybe a better pilot could get it to work?). Cheers, BiPod.

That is exactly right. You do get an indication that you have set an SPI. A "wedding cake" symbol appears in the TAD (sort of a white podium shape). It's a bit subtle if you have yours eyes glued to the TGP MFCD though. BiPod.

If by "holding" snapviews you mean holding the key down while trying to fire, then I beleive you are right, the gun will not fire*. You can latch the snap views by pressing RCtrl-Num0. Then press once to go to hud view and..."Guns, guns, guns." You can definately fire in HUD view, that's my standard method. RCtrl-Num0 again to unlatch. *I encountered this problem while SST programming my x52. IIRC You couldn't fire with a change view key set to down. I haven't tried the keyboard method so I could be wrong. Hope this helps, BiPod. EDIT: I have now tried with the keyboard and it fires perfectly for me in all cases. So I can't help, sorry :(.

I was going to keep out of this one as post 3 did come off as rude to me, but I will give Woots the benefit of the doubt..."just a little ribbing". I'm sure others have taken my jokes the wrong way too:). I have the same problem as Woots. LAlt-C just makes the cockpit unclickable. The cursor may or may not change to the windows mouse cursor, but it never vanishes. As a work around I have mapped the mouse to my Saitek x52 so I can move it off to the side, but it's still a very annoying bug for such a simple problem. I can live with it, but a community solution would be appreciated:). DCS A-10: 99,999 great features, one tiny bug. Lets start burning! :furious: BiPod.

True, but to further this you can put an icon at any point on the TAD. -Make the TAD the SOI -Set the CDU STEER PT selector to Mark (or do it on the UFC) -Slew the cursor on the TAD where you want to designate an SPI -Click TMS Right Short to create a mark point. -Then hook this as per Nate's post. Hope I haven't stepped on the toe of a giant;), BiPod.

Thanks Mugenjin, I almost made an ass of myself by preparing a long post about laser rangeing until I saw your post. To summarise Mugenjins link : It's a bug Heres a great video on laser ranging anyway: 12 mins long, but very good. BiPod.

I've also had this problem with my x52 and I have read of others with the same issue. The plugs connecting the two units my be loose causing the LEDs to flicker and the stick to fail. I can usually just reconnect without a problem. If your plugs are too loose may I suggest blu-tack or something else to hold the plugs in place. Of course, it may be a more serious problem, but I suspect that its just the cable. Hope this helps, BiPod.

Spot on nomdeplume:thumbup:. After reading your post I gave it a go. Clouds were IR transparent up until level 8 then opaque at level 10 (maximum). Ditto for the rest of your post. I deliberately chose tiny clouds for my pics above so you could see their edges on the CCD images, but it works on much bigger clouds. @Rextar I checked your mission in the editor and it is level 10 clouds:( So this entire thread is no help to you:(, but at least I learn't some stuff even if no one else did. I can't run the mission in question (crashes on loading) but the editor says the clouds only come to 1400 meters (4600 feet) and the target is on a summit at 6000 feet ("above the cloud deck"). So it should be poking through. I won't help you any further as I can't run the mission, but are you sure you are getting the coordinates properly from the JTAC? BiPod.

Perhaps the OPs clouds were just too thick, but as you can see here both the TGP FLIR and the IR Mavericks have no problem seeing through light clouds. @ Slugg88 There seems to be a lot of people out there that agree with you, so maybe its not a simple issue.

It is. I've done it. (Jumps up and down hoping I'm not just insane.) ...but to quote myself from post 3 "I don't know how thick the clouds have to be before the FLIR will not penetrate." BiPod.