johnb263

Ah Ok. I never use presets so did not notice this - the default setting must have changed. That also explains the "1" on the front left uhf display, which looked suspicious. Thanks for the effort, appreciated. Radios works fine, as you say. Just got downed twice, so everything must be OK otherwise. Thanks for the great support, and apologies for wasting your time

Thanks a stack ChillNG. Avoiding openBeta since “xr neck safer” is broken with native openxr, and really I cannot turn my head 100 deg looking down without injuring myself. Btw neither voiceattack or neck safer was running during the tests

Thx for the quick reply :- yes, by “middle radio” i meant the old radio below the arc 210. I found some post where it was mentioned the Arc210 couldn’t be used for Wingman comms in this campaign

Hi, I'm on mission 12 of the campaign, which I'm really enjoying - but, after the latest stable, standalone (not steam, not multiplayer) update earlier this week that includes the new arc 210 radio, I cannot get any communications going with the wing man. Seems like the Lavan tower works OK (using the new radio at 141.6am - I need to set fm, not am), but tuning the middle radio to 260am for the wing man does not work. Cannot hear myself, and cannot hear the wing man. Mission will not proceed from waypoint 2, wing man just keep circling. So basically the campaign is defunct, it seems. It's not a sound issue, everything else seems to be in working order. This is not using the MT executable, just the regular one - I tried MT, same problem, plus a few others. Also tried mission 11, same problem. I also tried another campaign, a10c iron flag part 1, mission 1. All frequencies work in this mission (there are 9, UHF/AM/FM). I used all three radios without any issues. I did a dcs repair before testing again. While I'm flying VR, I tried with regular 2D flatscreen and it also makes no difference. Attached track of Mission 11 (scud alley), takeoff to WP2 demonstrating tower but no wingmen... Also system specs. Apologies for the long post, I wanted to make sure all information is there in case I'm doing something wrong - great campaign, want to fly missions! Any workaround will be greatly appreciated. Thanks in advance DxDiag.txt tempMission.miz.trk

Is there a quick way to preview a mission (.miz) files - to determine if it's ramp / runway / inflight start, without loading the whole thing?

Mouse wheel dont work (most of the times), makes it tough to turn knobs (In A10c world). Dragging a knob sometimes also wont work. I get a "bing" every time I press a key.. and some missions will hang on load (like summit at tblisi)..

I attach a track - funny thing is, the track goes haywire right about the same time the Mav targeting goes wrong. When I was fying, the first Mav launch had no problems, then I proceeded to the next (Jtac designation). When I locked onto the second target (SAM of on the end of the lineup of trucks), and then slewed the Mav, it slewed both the TGP and the MAV off target. Not to the first target, but off the SPI to some point. I lased when designating SPI, so should not be parralax. I'ts here where the track also goes wrong (at least when I play it back). Seems to me some bug or some procedure that I'm following... I also tried to use the TAD to lock, but it did not work (even though I reported before that it does).. Opstarvation_v1111.trk

I understand - make TGP SOI, move point over target to track, TMS forward long to make TGP target SPI, then china hat forward long (still with TGP SOI - right?) to slew Mav to SPI. The "TGP crosshairs" you mention is the same as the point in pointmode over the target - am I right? If so, then the point is where TGP is SPI after china hat forward long. So the point is actually important, since this is where the TGP is locked, the same point that will become SPI, and where the Maverick head will slew to once china hat forward long is pressed. This is what I'm doing - my previous post just "proved" that I had to have TGP as SOI to be able to lock, make a SPI and slew. So, as I mentioned in the original post, I will TMS forward long to make TGP SPI. Still, with China hat forward long, I slew to something else. That's whats confusing me...! No matter anyway if I make the Mav view SOI before china hat forward long. same thing. No matter if I lase when assigning SPI to eliminate parralax. Same thing. Only happens on third or fourth target. And from then on, I can forget to assign a new SPI on the TGP screen for the rest of the mission. I must admit I've not paid attention to the diamond in the hud in general. Sometimes I check it in the TAD view. So that's a good idea. Also will try to remove SPI before assigning a new one. I can also try to borehole the TGP before slewing to a new target. And assign TMS forward long to a keystroke to see if it's the Hotas malfunctioning. I hope they add a GAU-8 to the

Thanks for the reply, Speed, but - I know TGP must be SOI, otherwise I wont be able to lock onto the target (or move the TGP head with the throttle joystick), and I know it's locked - since, in the TGP screen, the point is following the target (for moving targets) - Also, I can get rid of this problem by slewing onto static targets in the TAD view - which cannot of course be done for closely grouped or moving targets, and anyway often there's no time for that - could be some hardware issue I think, unless it's a common bug, but I dont see any unresolved complaints in previous posts on this issue.

When slewing onto a target in the TGP (TGP SOI, point mode on target, TMS forward long, china hat forward long), the maverick seeker head will slew onto the target first time. But, it often happens when moving onto a new target, locking it (point mode, TMS forward short, TMS forward long - and I mean long, like 5 seconds, TGP SOI), both the next maverick seeker head and TGP will move to the previous target with china hat forward long. This is fustrating when pressed for time, trying to lock onto moving targets or selecting between closely grouped targets if the plane's nose isnt pointing directly at the target (to better manually slew the Maverick seeker). Is this exptected or am I missing something? Been like this for the past 3 or 4 versions.. I'm using a hotas Warthog, I thought it could be that the tms forward long does not register, but I checked in the cockpit view and it shows the switch moving forward. So I'm lost. It kinda spoils a otherwise great sim

Since 1.1.1.1, on ramp start, turning on battery power, then floodlight, then, when turning on the inverter, horn goes off with flashing oil pressure. What am I missing? track attached. Used to work fine before. Mission = dawn patrol.. startup.trk

was flying one of the "instant action" missions, wingman got damaged, I thought he was down. At one point he came up on the radio, but when I asked to rejoin I got a "negative". Either way, eventually I also got grounded, so the sim switched to the wingman. He was happily taxing back 60 miles to the runway, noise in the air (since his nosewheel was shot). Hey, why not! :lol: