doveman

This has been with standalone (probably third-party) missions, I haven't tried the Campaign yet. This particular time it was with Night_PatrolMPx2.miz (I actually had to load it into the ME and save it as a different name as it was hanging when trying to load before) but I've experienced it on every mission where the ATC has told me to contact tower I think. On this one, after I got right over the runway, I was given permission to land and after doing so I was told to taxi to the parking area, which is why I thought perhaps that was a requirement before I could complete the mission. I can probably recreate it just by taking off and coming back and contacting ATC to tell them I'm inbound, so I'll try and get a track for you.

Oh well, never noticed as I just use RALT+\ all the time. I think it's \ on it's own that shouldn't do anything when not using easy comms. Either way, it doesn't help with my problem.

That's not odd. I have to use RALT+\ (or OEM102 as DCS sees my \ key!) to use the radio at all if I'm not in Easy Comms mode. Don't see Tower in the menus though.

Ah thanks. I've never noticed that shows the percentage before.

OK thanks, I'll just have to decide when I've completed it and congratulate myself then ;)

After I contact ATC to tell them I'm inbound, they give me a heading and tell me to contact the Tower when I'm nearer. However, there's no separate radio menu for Tower (I think there used to be judging by the old manuals) so I just use ATC - Request Landing but they never reply. When I get right above the runway they seem to automatically contact me and give me permission to land though. Also, on missions where my objective is to fly to another airfield, the mission never seems to end automatically, even after I've taxied to the parking area and shutdown my engines and I have to just Quit it. Is this normal or should there be some sort of success/mission completed screen/message?

Hi Erforce Could you add this bug please, where the mouse cockpit no longer works after pressing Esc and looking at the Briefing? http://forums.eagle.ru/showthread.php?t=101243 It's completely reproducible for me and a complete pain in the ass, because it means I can no longer operate the shark and have to abort the mission, therefore losing all my progress (as there's no save function).

+1

Thanks for the explanation, that should help me get my head round it ;) So the main point is that the direction is an absolute compass bearing (ie 270 is due west) from the bullseye. As you say, the tricky part is working out how to get to there from our current position but I'm sure it will come with practice.

I'm probably being stupid but thinking about it, how do I know where the 0 point on the bullseye is to take the direction from? What I mean is if I'm approaching the bullseye from the west then the 0 point could be in front of me and 90 would be to my right, which would be south but if I'm approaching it from the south then 90 would be to my east. So if the direction given by the ally is dependent on his position to the bullseye, I'd need to know his exact location to know where he means.

Ah thanks, that will help me work out what he's talking about :thumbup: I think I know the target marker you're referring to. It's the one I can set the PVI to I believe.

Yeah I guess I'll have to tune it out when it gets too annoying. I don't actually understand what they're telling me anyway, which doesn't really help ;) I presume the "bullseye" is a heading so if he says "bullseye 124" does that mean if I turn to 124 degrees that I'll be facing the target?

Tried both suggestions and neither helped, mouse cockpit is disabled after viewing the briefing. I seem to recall this was a problem a while ago but that it was fixed. Seems like it's crept back in. Very annoying not being able to check the briefing whist in-flight :(

I found the "Disable Allied Flight Reports" option but then I didn't get any messages, even from my wingman (other than when I radioed him and he replied), so that's not very good either.

That makes sense as well. Either way it's shooting at my side :smilewink:

I don't think it's that strange. If the sim is still producing varying framerates, say 30-50 and just the driver is limiting how many are actually seen via double-vsync then I guess in the background the fps being generated is still jumping up and down, which then causes the microstutters for whatever reason, whereas if the engine is also limited to not producing more than 30fps, this wide variance doesn't happen at any point.

Thanks, I'll give that a go then.

Ah that would make more sense, shorthand for "Defending myself from" :doh:

You're obviously more advanced then me and can work out what's going to happen from the briefing ;) It seems perhaps that's what was happening (the repeat bug) for me on that mission as it did seem rather excessive.

Thanks, I'll try it although I've read reports of people having other problems with aero disabled so I'll try the small taskbar icons first. I don't really like them that small though so it's not going to be a long-term fix for me.

I upgraded from Cat12.6 to Cat13.2beta3 last week and on Sunday I was getting loads of errors on booting and was no longer able to launch either Arma2OA or DCS World. I reinstalled Cat12.6 but that didn't help, so I had to restore a True Image backup from about two weeks ago and then it was fine. Might have been nothing to do with 13.2beta3 though, as today I'm unable to run Arma2OA again even though I was playing it fine last night. DCS World is still working though.

I guess us ATI users can use Radeon Pro's Double Vsync option to do this. Do you disable Vsync in-game?

I'm not sure but it might be after pausing the game and opening the briefing but whether it's that or not, something is causing the mouse cockpit to stop working mid-game, so that I can no longer look around or zoom with the mouse.

I'll have to check as there are some supporting MIGs in that mission I think, so it could be them rather than my wingman. I'll look for that option though and try disabling that, thanks :thumbup:

I really don't find it useful at all. If I keep getting distracted every five seconds by the AI calling out his contacts and have to look at the subtitles I can't concentrate on setting up my target in the Shkval or whatever else I'm doing and I don't have time to process the information or think if there's anything I can do about it before the AI calls out another target, so it's just a useless and annoying stream of noise to me. Information is only useful to the extent that we can process it, so we don't have our current position and altitude being read out to us as that would just drive us mad and it's better to have this information available for us to check when we want to. Similarly, if the AI wants to send his targets to my targetting system that's useful but it's just distracting having him constantly calling out every target he sees.