VAF [136] Striker

Definitely a DCS late activation bug. We've tested it extensively and if run the exact same scenario (no mods, no scripts), the ships are complete if started at the beginning of the mission and disappear if you have them late activated. The late activation we tested is just the normal mission builder setting. If you leave the server and come back in they appear normal.

If it's late activation you're using it's that bug that's been brought to my attention. We've encountered it as well. I posted the same problem back awhile ago. According to Bignewy in another connected thread the problem has been reported. https://forums.eagle.ru/showthread.php?t=246061

The VAF is looking for a few pilots to join our ranks. We will be taking attitude before skills as skill can be taught. We are looking to add to our Squadron roster, the F/A-18C (VFA-136 Knighthawks, VFA 131 Wildcats) and the A10C (75th Tiger Sharks). The squadrons will be supporting each other in our missions that are fun but require a high level of cooperation. We are looking for anyone that has a good attitude towards being cooperative and willing to take the time to go through some basic training. Comprehensive training will be available for those that want it. We're not looking for quantity; we are looking for quality individuals. We only consider a couple of candidates at a time in order to support their training and enrollment in the VAF. We like to take some time to access the candidates fit with the squadron and provide the basic training to become a VAF member. We plan to evaluate and potentially recruit on a quarterly basis however as mentioned we are not looking to just create numbers. We focus on realistic training in our Student Undergraduate Pilot Training program which starts out with VFR, Pattern Work, Close Formation and then moves on to IFR, Formation Work, Refueling and Weapons Training. Progression through the blocks is at the students pace and flight status will be based on the ability to fly safe and to adhere to some basic operational standards. We fly primarily in Caucasus and Persian Gulf but also do some training and combined operations in NTTR. We are a mature group of pilots so we're looking for individuals that fit into our current group and share similar attitudes and personalities. So if you if you feel like you are a mature person and have the patience to learn but also have a lot of fun and laughs with some great people, please go to our website and submit an application. We'll get back to you right away. Please make sure that you read the rules carefully before applying. We are North American (US & Canada) based and are on almost every evening from 7PM EST till 10 or 11PM EST and are on most Saturdays and Sundays. Please PM me if interested and we'll send you an invite to our Discord channel.

There's an actual end or conclusion to the campaign but you can continue to push further if you want.

Welcome To Operation Khachapuri! NOTE: Mission has been updated to 2.0 https://www.digitalcombatsimulator.com/en/files/3306205/ The Virtual Armed Forces along with our partners the Black Veal Squadron are pleased to announce our first public release of a multi-role muliti-mission dynamic campaign. The campaign is actually a single mission with randomly selected mini missions within the campaign. It also includes CTLD for transporting troops and other assets around the battlefield. The file is available on the digitalcombatsimulator.com website. The campaign contains custom voice over work for all of the available missions. Any comments, questions or suggestions will be welcome here. If you are having problems running the scenario, please post your system specifications and how you are trying to run it, dedicated vs client host. We recommend running this on a dedicated server without server side mods, with 3d rendering off and with 32GB of ram. Please send me a private message with your email so we can send log files or screen shots of problems and suggestions. Many thanks to all that helped with testing and to those that provide the great scripting tools we used to create the mission environment.

Nope, go to your installation folder and open a command prompt in the bin folder and type in DCS_updater.exe update @openbeta This will just change your installation to the beta install with the latest patches. You can toggle back if you decide you don't want to use beta by doing the same thing but changing it to @release. Pretty sure most of this guide is still applicable. https://forums.eagle.ru/showthread.php?t=114030

Thanks Bignewy. I appreciate this is finally being acknowledged. I use the A-10C all the time and it's a really frustrating problem.

Problem is still happening, even worse now.

Yeah, it's a little confusing about exactly what combinations work but I'm pretty sure you need at least the "command, cargo ammo & fuel".

I'm pretty sure you only need a power vehicle if you request ground power but I'm not totally sure. If you figure it out I would like to know. I've never requested ground power on any of the choppers except for a long time ago when I was doing a repair at a FARP. I haven't been able to identify a Western ground power vehicle.

There's actually a good post that explains what you need. It's old but still applicable. I've been using them kind of like a template for awhile. Having the unit side (blue/red) set correctly is part of it but you also need to have the correct vehicles. For example if you land a Huey at a FARP with the wrong units you won't be able to refuel or rearm. https://forums.eagle.ru/showpost.php?p=1551405&postcount=1 What you need are a command vehicle, a fuel vehicle and an ammo vehicle. You can also add the FARP fuel and ammo dump but they don't always work. What I use are listed here. For Eastern choppers: Zil131 APA8D power ATZ10 Fuel Ural375 cargo SKP11 command For Western choppers: (haven't needed a power vehicle) M1025 command M818 Cargo M978 Fuel Additional Vehicles for effect: ATSP6 Fire Truck GAZ 3308 And some other combinations of vehicles will work as well so you have to kind of play around with it. A good standard guideline is to use Russian or Georgian vehicles for MI-8 and KA-50 and use Western vehicles for the HUEY. Not sure what works with the Gazelle.

Have you tried running DXtweak or something similar to see what your stick orientation is before you start DCS? I ran into this problem before with an older controller and I found that it was a calibration outside of DCS that was actually causing the problem. Also, when you get into the pit, do you calibrate your controls by moving them before you start up? Just curious because I've found that in sim calibration is separate from outside in some cases.

I've searched and came up with a couple possible solutions but they don't work in my case. I'm posting here and hopefully someone can help me diagnose the problem. This only happens on the Hoggit Caucasus server. I can join the PG one fine. I can see the server on the list perfectly fine but when I join I get a persistent black screen. I've waited up to 10 minutes and nothing. I've tried changing the swap file allocation and location. I'm running DCS on an SSD drive. I've tried a complete uninstall and reinstall. I've done a cleanup and repair. I've replaced my video card and monitor. I'm not running any AV software, only Windows Security Essentials with exceptions for DCS. Super clean up and down and the proper ports set on my Comcast account. I'm hard wired into the internet. I am on Windows 7 64 with plenty of memory and get decent frames on our servers. I'm really puzzled why this will only happen on this particular server. And I was able to join right up till there was a big release of the Hornet systems. I can't remember exactly but I think it was back right around the time that the HARM was released. Added my log file. hoggitlog.zip

Any idea if there's a fix for this problem coming soon? Going on for almost 2 1/2 months now.

I'm not disputing your expertise with IR at all and problems seeing objects in certain environments. My point is that this is obviously a graphic representation problem as you can see very clearly in my series of images. That's why the thread was started to begin with.

Gentlemen, no one here would ever dispute your expertise when it comes to FLIR technology. For any of you guys that have used it then you're lucky to know the facts about how it works. I have seen many IR images over the years in my work in graphics and photography but I would never consider myself an expert. However, this is not a problem that is related to the actual FLIR function. I've been using the A-10C since just shortly after release and although the original DCS World was no were near as advanced compared to 2.5 and speed trees, you could at least see stuff. I know that they're working on the FLIR rendering code but we keep running into visual problems that make it extremely difficult to do anything in the A-10C or the Harrier. For example, I can't find a tank inside an urban area with trees now like I used to be able to. It's extremely frustrating to try to do a mission where you have to search and all you see is bright white objects. So I'm posting this series of images so you can see the actual problem. You can see as I approach an area with trees that some of the sprites (whatever you call them now) or leaf sections on the branches are glowing. When I go to CCD they are black instead of the same as the other leaf areas. As I get closer the areas that appear to be white actually start to melt away and when I'm within a few miles they disappear. The reason we keep posting stuff like this is because it is a visual and annoying bug. I know they're working on it but it's important that we keep showing them what we're seeing.

Exact same thing is happening in the A-10C and the F/A-18C. I was originally going to post it on the A-10C bugs section but it looks like this is a global problem with the Litening pod now. It looks like specific leaf sections of the trees are glowing white.

Please add the USS Dwight D Eisenhower to the liveries for the carrier module.

RGR, I set it at "Range/Relative Bearing" and I'm assuming it's from off the nose and if you guys say that the nose is up 4 degrees then that would be 180-139+4. That would be 45 degrees, correct? Yes, and it would be nice if we knew this were going to happen. I wouldn't have posted it as a bug.

OK, so here's a picture of my Tacview showing the exact time that the TGP was masked at 7:52. I did a select jet of some BDU's to time it and they came off the rack at almost exactly 7:54, two seconds later. If someone can explain to me how to get the slant angle, I'll post it. I'm not very good with the functions in Tacview. But that looks pretty darn close to 45 degrees to me. I know it can be deceiving though so I would like to get the exact angle.

I was flying level and not even close to 40 degrees but I'll check it again. I didn't have a non static object on the airfield so I can't see the angle in Tacview.

Something weird is going on because I tried the IR pointer and it's not coming out of the lens but rather between them. It's like the ball is off some degrees from the actual camera lens or view angle.

I think that they need to check the set angle because I was only about 70 degrees off of the target at 10,000 feet when it became masked but I'll check it again.

Since the introduction of the TGP for the Hornet, the TGP in the A-10C gets masked when it shouldn't be. An example would be when you are at an altitude of about 10,000 and at about a mile from a target and flying directly away from it, the TGP suddenly is masked by a grey box. I know for a fact that it wasn't doing this before the introduction of the TGP on the Hornet. Also, the trees are looking a little better, not quite the white hot pencil sticks they have in the past under certain conditions, but I noticed that parts of the trees in the leafs are showing up as white hot graphic areas attached to the tree branches.

You're welcome. I really don't see that changing it to a SA-11 changes the spirit of the mission significantly but I'll probably get some purists jump on me for that comment :). Anyhow, that was my solution.