guitarxe

I'm keen to try this out, but I've had a pretty traumatic experience with the carrier crew since it's been released, and really wouldn't want to be forced into using it. Does the campaign require to use it or no?

I think which one is for A-10C and which is for A-10C II is in reverse in your post, but this helped me, thanks and cheers!

How do you reset this once you've done it? I've tried playing around with this, but the end result is worse than the original settings (putting the head further forward to see the hud means that you are that much loser to all the instruments and seeing them from a greater angle when looking down, making it hard to see them, and you can't even see the top row of the MFCD buttons because they get obscured by the cowling).

Having the same problem. Need this one fixed ASAP! Whatever other bugs can be worked out in time, but not being able to disable the broken deck crew means not being able to use the carrier at all! Our squadron isn't able to fly missions any more because of this mess.

Okay, but outside of DCS and the context of coding, this is the same pod, right? And since this feature exists in the implementation that they have for the A-10C, but doesn't for the Hornet, then it should be reported as a bug, right? Because the Hornet is out of Early Access now, so features like these are expected to be all implemented, this is why I'm asking about it. I guess it doesn't matter very much since you should be using ATFLIR most of the time instead, but still important I think. I read some other posts on the forum that mention that ED Team used a Spanish version of an older Lightening pod that supposedly didn't even have MSI. So if that is true, and if that pod doesn't have this feature, then I guess this would be considered correct in terms of what they modeled it against, but they should at least clarify that somewhere, at least in the manual. There are stuff in the manual that say things work one way, but then in DCS they don't work that way, and it drives me nuts. What is the source of truth?

Oh, not implemented yet? I thought the Hornet was out of Early Access? Anyway, since it works in A-10C, how come it doesn't in the Hornet? It's the same pod, isn't it? Just curious.

In the manual, on pg 245, it is described as follows: [quote]Laser Type. Pressing this pushbutton cycles between laser types: MARK (target designation laser), PTR (infrared pointer, used to visually point out targets at night), and BOTH.[/quote] However, if I push the OSB above the words "MARK", it simply boxes it and unboxes it. It does not seem to cycle between the modes "MARK", "PTR" and "BOTH". Is this something that is not implemented in the Hornet? I know that in the A-10C you can use the Lightening II to point targets with an IR laser, so I thought this was the same for the hornet.

Not to sound too paranoid, but are the files for the mod hosted anywhere else? Mediafire is one of things I learned never to click links on...

I want to practice formation flying with an AI, but I'm having trouble figuring out how to get the AI to use the same IAS throughout the flight. There are options to set fixed speed between waypoints, but it seems to be locked to GS only, and I can't change this. So this means that throughout different altitudes during the flight, the IAS will change. I do have the waypoints vary in altitude throughout the flight so it's a bit annoying having to guess what IAS the AI is flying all the time to maintain correct separation. Is there some way I can get a desired fixed IAS speed between waypoints?

I might be doing something wrong because I'm fairly new, but I'm having some trouble with clouds. In particular, the fact that the clouds are covering target areas and I can't see through them, and that the clouds are sitting at only 5,000ft so going under the clouds I'm in great danger. I am suspecting that this might something with a recent version of DCS, because when I look at youtube videos of others doing the same missions, they don't have these clouds at all. There are a few sporadic poofs at much higher altitudes, but there in those videos the pilots are sitting comfortably at 10-15 thousand feet sniping things with Mavs and JDAMS, but when I do the missions I have to search for breaks in the clouds to even be able to see the enemy. Can someone confirm please if that is the case and is there some way that I can force the missions to use older clouds?

Awesome, thanks for answering! Going to get these tonight

I am talking about these ones: https://www.digitalcombatsimulator.com/en/shop/campaigns/a-10c_bft_campaign/ https://www.digitalcombatsimulator.com/en/shop/campaigns/advanced_aircraft_training_qualification_campaign/ https://www.digitalcombatsimulator.com/en/shop/campaigns/a-10c_ttq_campaign/ I want to purchase them, but I notice that they have a requirement for the "I" version of the A-10C, not the "II" version. This makes me worry if these are current and will they work properly, has anyone done them recently? I was looking over the posts here and there are lots of people posting about this or that broken in some kind of campaign here or there. Sometimes they say it's because the Caucasus map had changed making the mission impossible and stuff like that.

Thanks WipeUout, I used the shortcuts described in that exact topic. But actually I just realized what my problem was, it was PEBKAC as usual. Somehow I set my SteamVR settings to be like 5000x5000 resolution per eye. Didn't even notice that I had done it. When I changed that back to default, the game is working fine now. Still have some visual problems that I need to figure out and tweak, though. Like things don't look very good when at high speeds. They kind of like "wobble".

So I followed the instructions to create a shortcut that does "--force_enable_VR" and also I tried with both either "--force_steam_VR" or "--force_OpenXR". In both cases I have a problem that when the map loads the game stutters impossibly. I am not talking about just low FPS below 60. I am talking about the game is rendering like maybe 1 frame per 5 seconds. It's so bad that I can't even move the mouse cursor across the screen. I don't know what's going on! I have the game updated, I tried both with the MT exe and the regular one. My VR works fine in other games, but here it is crazy like that. I searched for other topics with similar issues, and someone commented about issues with some kind of Asus software for lighting up RGB, but I don't have anything like that and I didn't find any other answers. Anyone ever have this kind of issue before or could suggest what else I should try? My system specs: i9-11900k 32gb RAM nvidia 4070 ti DCS installed on an SSD

All the more reason that a lower resolution in the VR headset would achieve higher frame rates, is it not?