BMGZ06

Ya easy comms is on and I tried flying right over the carrier with no joy. I got it to work once but then never again. The other carrier comms worked last night before the update to DCS. I also tried Marking Moms call and got same response. The carrier cant be set not to accept recovery since it is a mission designed for case 1 recovery practice by ED. The normal in games comms menu works calling inbound just fine.

I am looking through the manual and things are just not clear to me what is going on with the commands. Testing out the new ATC commands extension i bought with it and in the SC case 1 mission when I call "Inbound for Carrier" with easy comms on I get the response " Go to alternate". The radio freq is correct when I make the call at 127.5. The tanker responds to the " Approaching to refuel" and the other commands. I can also get the ball call, overhead call, and abort inbound to work. I am not sure how to use the Editor in Vaicom to complete the Finish process at all. Says to go to the profile and replace the When I say text with the text copied to clipboard. I did that and still get the go to alternate for inbound calls to carrier. I tried to say the name of the carrier as well. If anyone is able to help in discord or teamspeak please let me know.

Here is the log file which is the one you wanted I think. I also just saw the .cfg command to force a the full log for future crashes and enabled it. dcs.zip

Thanks for the help NEWY. I will look for the log. Is there a reason or something I need to change to allow me to click on "OK" to send the full crash file to ED when it pops up after the crash? No matter what I do I can not click on OK because the mouse cursor disappears once I try to get it near the dialog box. This is because the cursor gets confined inside the VR window I guess. I cant hit enter to send it either. I will also try a video driver update or is there known more stable driver that is older than the nvidia 442.74? I did have the card OC'd but had already put it back to stock before this crash happened.

I have the same issue. I bought vaicom pro and you can force the command verbally and it works well. I can launch turn into pattern, make inbound call then also has the overhead call, hornet ball call. I would normally only be able to make inbound and see you at 10, then nothing more. It has all the case 3 commands and many others. I use it in conjunction with Baileys F18 v2.0.vax profile which is awesome also.

This has happened in the F18 3 times so far. I have the yellow donut and I can get this slow call still.

I tried giving it 30gb of page file and nothing changed performance or reduction in crashes. Since this last update the crashes are frequent and others I fly with are having the same issues. I think there is still a major memory leak or something else causing the game to want huge amounts of memory.

Yes monitor users have the opposite issue. You guys can see the deck lights at beyond 2 miles though and VR users can't. If they are working on it then that is great. Hopefully they figure it out.

preload radius I meant.

Since last update I get crashes and it is normally when trying to swap roles to another plane. The only file log I saw is attached. The other issue I have is trying to submit the crash report. Maybe because I am in VR but when the crash message comes up and asks to click OK to send report I cannot click it at all nor use enter to submit even though the OK button is boxed as the selection. If I kill VR then DCS just closes and the message closes as well. dcs.log-20200525-010435.zip

I thought it was a bug as well but it isn't. The grading system is watching where you are pulling power and we are all doing it in the wrong spot. I have now trained myself to make sure I am set properly by the time I get in close so I can just maintain power and then add it in right before I touch down. Most people are adjusting back over the wires and then are late adding it back in after the wheels hit the deck. I am not getting EGIW anymore. Consistently getting OK 2 3 or 4 wires with no other letter soup after that. You will get the feel for it but you have retrain your muscle memory over the ramp.

The landing deck lights are only visible from about a mile and the meatball is very very bright to the point that it is not clear where the ball is in relation to the datums until I am about .5 mile or less which leaves little time to adjust. I do not rely on the ICLS as it can lie and the ball is the ultimate reference or is supposed to be at least. Are both of these intended to work this way? I disabled the FLOLS overlay in VR due to the size it displays takes up a lot of real estate and is very distracting. You can see my hardware in signature. I have tried various graphics settings with no luck. View distance is set to extreme and preload radius at max. Bloom setting in VR options menu is unchecked. Gamma does nothing as well.

I have now made it habit to slowly add power over the ramp and tehn go mil just before touchdown and no EGIW or other EG grades. Finally getting (OK) passes with no other letters to make me depressed. Still hoping there is some fix for the crazy bright ball light that makes it impossible to see if im high or low until in close when the bloom or glow effect goes away. Also cant see deck lights at night until 1 mil or less. Someone else in the server last night had the same issue with deck lights who doesn't use VR. It seems to be a render distance issue.

THis was happening to a bunch of us in our mission training last night. My and several others had the Tpod slew to WPDSG and lock on initially then they just stopped responding. Cage/Uncage just went tarded. Then a few others had the Tpod slew but then could not actually release the GBU-12's. this has been happening since before the last update.

Yes I noticed this as well. AI followed me and ran into me in the groove. Then another time he slammed into the back of me landing on deck. Also the wind direction in that mission is not right if you are using the Caucasus mission. Wind is over the bow so there is a 15 knot cross wind. BRC wind is 304. If you noticed the plane wanting to push to the left hard that is why. I noticed other issues in missions so I just avoid them now and make my own to practice or go into servers that I know are setup properly.

yes that is very clear. makes you wonder why that is so clear from 20 miles but not the deck lights or ball

The Ball in the Reverb looks like a dying star to me until I get less than 1/4 mile out. I cna not tell if it is high or low until it is too late and at night it is worse. Also the Deck lights on Supercarrier do not render into view until about a mile or so. Is anyone else noticing this?

That is a big difference. I have been looking for a way to adjust the brightness of the ball in VR. It is crazy bright for me to the point it is useless until the plane is close in to the ramp. I have adjusted every graphics setting in game and nothing works not even unchecking the bloom feature in the VR options menu.

Ya maybe that is it. It is pretty bright in my room though but maybe it needs more light.

FLOLS lights are already too bright for me in VR. Cant make out where it is due to the major glow washing out the green lights until im in close at the ramp.

This is what I am seeing with the Reverb. I do not get this flickering in steamvr house or the windows mixed reality demo house and both stress my gpu to max clock speeds. This is the fastest and easiest way for me to post the video since I hate uploading to youtube. https://drive.google.com/open?id=1-JT8Qlkn0zr7WubjToOeR4YcnM0wvZPJ

That is good to hear. For now I just call ATC and go through the comms again as fast as possible. Normally works and I still get the LSO grades. Hopefully I don't get my wings clipped.

That sounds fun. I would like to try that out. I have no idea how to install that MOOSE stuff though

No not different weather, they are just F'n Pro's.

I just did a landing in my squads server with wind over the landing area as much as it can be. I was able to get a (OK) 3WIRE (BC). No EGIW. The reason is in the missions ED made the wind is 15 knots over the bow and creates some turbulence around the island perhaps and screwing with line up and also makes you float or balloon up then you cut some power to arrest sink rate. Basically the missions have cross wind. By the time you hit the wires the engine response is not fast enough maybe and that is why it is picking it up as we are cutting the power before touch down. I am speculating of course. I know nothing, don't listen to me.:helpsmilie: