Moxica

Shoot. Tried same mission again. Didn't even quit after last post; Not working. Comms menu only working on ground.

Fixed it: Uninstalled VoiceAttack, DCS Cleanup and repair.

Yeah! Let it rest for a while. Maybe if we leave it alone an hour or so, the problems will go away.

To me as well. Some setting is set to auto, it seem. Probably in oculus debug tool, reducing quality to that ole mush. This is so frustrating.

I found the "Active pause" under UI layer. But the comms menu work only on ground, and including the JTAC. So I started the dialogue while on ground, but took off before I pressed "Ready to copy" Text still there while airborne, but F1 just affects the view. (F2 took me to outside view allthough the comms menu was still active) I fired on a truck, and got "Abort abort abort" from JTAC. But I can not respond via F keys anymore.

Moved, and is under "UI Layer"

Comms menu only works on ground. Active pause is not present in controls menu. JTAC scripts stopped working; Now reports "Passing waypoints" and targets only. I can not contact that same JTAC which worked before update.

This Caucasus training mission never had any performance issues. Now it looks looks this the first 20 secs or so: No textures, and ground is all water.

Also: Clouds now look like something from Microprose anno 1982, and JTAC does not answer the call. So far it looks like pure sabotage.

Did not measure, but a VERY disappointing drop in framerate on Oculus Quest 2; ah64 on my (former) smooth test mission, Caucasus. My new, brake-my-bank-account PC rig has held up so far, except for Marianas. But that mission was cream! I'm going to bed and now to have a taste of depression, because this runs like my old PC.

Not sure if this applies, but in Oculuis Quest 2, I look straight ahead, and press "5" on the numeric pad. This puts me on center.

https://www.google.com/search?q=eur+to+usd&oq=eur+to+usd&aqs=chrome..69i57j0i512l9.6154j1j7&sourceid=chrome&ie=UTF-8

No need to excuse. That is a good memory. I have tried LB2 on an emulator, and watched some movies on youtube. But that sound is enerving, and today, I could not hold out ten minutes. Most sounds in DCS are fantastic, (Except the wingman in target-rich areas) Sometimes i get Deja vu's when flying the apache. I can not point out details, but I'm pretty sure some actions are identical til the LB2. PS! What/when should I call out "Spot"? What is that; I am not able to spot any sparkle or laser beam. So I just hit it, not having a clue about its significance. "SPOT! ..i think" Edit: I found: CAS 101: Close Air Support Basics. – Task Group Warrior

Xcactly!

Thanx guys! I just made it work, thanks to you. Wow! This is so undescribingly cool!

Thanx a lot! I think that might have hit the spot!

Thank you. I've seen that video, but it avoids some critical points in my ignorance. I know the difference in lo/hi/dir etc.. I'm confused because I'm not sure if I was in LOBL or LOAL, because I have no indication on which mode is active. Also: I can not fire until I have a solid box; And I do not get a solid box until I'm in LOS of the target. Some info must be avoiding me, or hitting that teflon part of my brain.

I asked Casmo how to switch to LOAL. He said I was already in LOAL by default. I am in CP/G seat, SKR as acq source. How do I switch to loal? (If I am in LOBL, how do I know?) I've only seen those acronyms in the George dialogue.

I have recently had success in taking down targets with lasing help from MQ9 Reaper in a simple training mission I made. That was a lot of fun! In a new mission, I try to take down a SAM from behind cover. -Not so fun. I need to expose the copter too much. My question is; What do the sensor need to see before I can call "Spot"? I thought it would be enough to see the laser beam, but it seem I must have LOS to target before I can fire. That kind of defeats the purpose. I feel there is something I haven't learned yet. Is it?

I set up an Arleigh Burke to land on. Static at first, and noticed that the copter was sliding forward unless I held the toe brakes in. Engaging handbrake did not stop the movement, and it went forward until it stopped against the wall. I turned off the engines before that. Gave the Burke a waypoint, and 20 knots speed; same behaviour. Engines off, handbrake engaged. Bug, or have I done something wrong?

How do I get the corrected version?

Yes, I saw that. Thank you.

Phew! That solved a long standing mystery/frustration for me.

Thank you. I did not notice there was a solution. I don't think it will do the trick, though.. Yellow George wheel = cease fire, not? Must check if there is another way to order him to cease fire.