Frogfoot1606687865

Bahger, Thanks for a great mission. Much more realistic than some. I played twice, once with realistic radios and once with easy radios. When playing with the realistic radios option selected I never managed to contact the JTAC. I could select UHF- JTAC- Axeman in the radio prompt and 'sign in' reading him my position, loadout and loiter time however however many times I tried he never responded. All the other comms worked well, and I really liked hearing the chatter from the f15s and the UH60s. When I played with easy radio the JTAC worked fine and I managed to level the bunker using his laser.

In TARGET press 'Get firmware' on the picture of the stick

Current state of closed Beta Hi, here is a question for the official Beta test team. I was wondering if the current beta build has resolved some or most of the crashes that seem to be so prevalent in the current open beta 3? I'm not sure what if any NDA the beta testers may or may not have agreed to so if you aren't in a position to say, just tell me to mind my own business :music_whistling: stability is on the top of my wish list for beta4 when it shows up. Cheers Tom

Thanks guys, you have both been a great help. Tom

Does the EGI have to be fully aligned, and SAS channels engaged prior to flipping the EAC switch to arm? I always wait until the 'INS NAV RDY' message is displayed before taxiing but have normally flipped the switch to arm some time before. Thanks Tom

Hi, I have noticed that when the EAC switch is set to ARM during the startup the EAC light on the warning panel remains illuminated, and for the first 10 minutes or so the autopilot.PAC etc is inoperative. Eventually however the light extinguishes and all is well. I understand that the EAC switch is solenoid held and can flip back if certain parameters are not met. I normally switch the EAC to arm after bot engines have spooled up and are providing power. And after the HUD BIT prompts to switch the EAC to ARM. I don't know however what specifically causes this delay between the system being initialized and the systems becoming operational. What systems are initializing that the LAAP is dependent on? Is there a way to speed up the process? Have I done something wrong? Cheers Tom

Serial #: Stick:00747 Throttle:00738 Location: Somerset, UK

Yes, A10 is much more GPU dependent than Blackshark. The most important thing is to have a balanced system (GPU and CPU both stressed equally) to get value for money out of your hardware. No point in having a super powerful CPU if the GPU is rubbish, and vice versa. With regard to your overheat problem, is your cooling fan on the GPU running flat out? I recently installed a GTX470 and noticed it seemed to be running a bit warm. I installed EVGA precision which allows me to monitor and create control profiles for the fan. I noticed that when left to its own devices the fan never went above 60% however hot the card got. So I created a profile to ramp up the fan speed as temp increased. Now the temps are 20deg cooler when under load. The added noise doesn't bother me in A10 as the sound blends in with the sound of the engines. Tom

Try running as administrator Tom

in theory you could find the folder containing the message and replace the audio file with another of the same name containing a very short quiet recording, or perhaps a 'mic click' sound.

My biggest hope for Beta 4 is much improved stability. Beta 3 is for me very frustrating. Only one in about ten missions goes without a crash. If not I think I shall be reverting to flying the shark until stability improves. EDIT: don't get me wrong I love where this sim is going, it is just so frustrating to immersed in the mission suddenly to be unceremoniously dumped back to the desktop.

If you set the autopilot control switch on the LASTE panel to ALT rather than ALT/HDG and put the A/C into a level bank then engage the autopilot it will maintain the bank angle and baro altitude, thus allowing you to do a 'hands off' orbit of the area of interest. Cheers Tom

TACview could do this in Blackshark, I dont know if it is compatable with Warthog yet. But I am sure once A10 WH has gone gold then Tacview will be updated. Cheers Tom

I think he is just demonstrating that the 9-line is listed as a message. He is pressing WILCO to accept the tasking, if for some reason he felt he couldn't perform the attack he would press CNCO. He is making the TAD SOI and then pressing China hat Fww short to zoom into the TAD, then scrolling the display to get the little red triangle (target) under the cursor, then TMS FWD short to hook the red triangle, then TMS FWD LONG to make the hook SPI Hope this helps Tom

I have had this as well, however I have noticed this more when I task The wingman to attack a target and he separates from me to prosecute the target. I assumed that terrain was masking me from the SAM that was painting him.

You decide what freq are to be saved. Just dial in a freq, set the preset to the appropriate number and press the 'load' button (to the left of the preset wheel) Then when you change the selector knob to 'preset' you can use the wheel to select your stored freq.

I had similar problems with my X52pro causing BSOD with saih075c.sys as the culprit when I started flying Blackshark, it would BSOD when pressing certain buttons. What fixed it for me to edit the profile and make sure all the descriptions for the macros/button press definitions were short and simple. (No special characters.) ie 'Fire Gun' not 'Fire GAU-8' 'Arm Eject' no 'Arm the Ejection seat' I think some of these long names cause an overflow in the Saitek software. Since changing my profile I went from BSOD nearly every mission to one every couple of months. Hope this helps. Tom

Master caution lamp illuminated? You probably failed to enable the EAC on the LATSE panel. (you will need to assign a keystroke to it as the switch is non functional in the current beta) Cheers Tom

I have to disagree with this post. Having a 4GHz Quad core I7 Processor and recently upgrading from a Gforce 8800GT to a GTX470. With the 8800GT (which runs Black shark at 60 fps on high settings) I had to lower resolution by a couple of notches and lower textures, turn down shadows/water, turn off HDR etc etc. With the GTX470 I have all the eye candy I like running at 1900x1200. I 'My' case the bottle neck was the GPU not the CPU. Make no mistake A10 can be VERY demanding on you GPU if you have a high enough resolution and crank up the eye candy.

If I recall correctly one of the buttons on the CDU is labeled 'LL' this toggles between Lat/long and UTM. Cheers Tom

It's not what it sound like in the cockpit that matters, It's what it sounds like with the Pilots headset on. I can't see how you could record what the pilot actually hears. however If you did record the sound in the cockpit, you may be able to approximate that the pilot hears by applying high pass/low pass/ band pass type filters.

Press Right CTRL and Return to display a little box with the Joystick inputs whilst flying. This will indicate if the axis centered or not. Cheers Tom

Well just to shake things up I will add my personal opinion. I have had the X52 Pro for a year now, and to be honest I wouldn't buy another one. The Second stage on the trigger has stopped working and the throttle response and the small slider on the throttle are very spiky. I get quite a few BSOD crashes which can be traced back to the Saitek drivers (quite a few reports of this on the net). Yes they are cheap, but in my personal opinion are a great product let down by poor quality control and shoddy drivers/software. I am going to spring for a HOTAS Warthog if user reviews are favorable on a few months time. Cheers Tom

32 and 64 bit versions installed at the same time here

That makes sense. However it dosent explain why some installations show ONBOARD and some show BORT #. Cheers Tom