ddwg72

One of the upgrades to the NA included a wide area visible hud. The same upgrade with the 2+. Below is a shot of a 2+ trainer where you an see the circles you see in the above pic are gone as the items reach almost to the edge of the hud. You can tell if you are looking at the older huds by the prominent circles. Be glad of the upgrade, can you imagine what FLIR on hud would look like on that older style hud.

I haven't done it so wont comment but if you need a work around TOO waypoint 1 after INS and it should work as a stop gap fix for you. I got in the habit of it and have not had any crashes.

That number is for casualty radius not kill radius. There is as kill radius and casualty radius for weapons. Kill radius is your are dead if you are that close if nothing is shielding you. Casualty radius is that is "can" cause serious injury up to that range if nothing shielding you. Not saying they don't need to be increased and really need it just that the kill radius is generally around 1/10th or so of casualty radius.

Cool video of the TAV-8 118/119 RPM on that move

I didn't think it was right either till I went to the charts. In the fleet, they almost never take off in a hover as they have to go up with so little fuel. It is usually a STO. You really have to look at the VRest pages now. If you want to know required rpm to take off you can look at NFM-400 based on weight.

Takes awhile to get used to but interesting to fly now. The current performance is well within the margin of error of an estimated performance chart.

I don't have one as I swapped to Virpil but if you need help setting one up feel free to jump on our discord and I can walk you thru it real quick.. Look for Roth https://discord.gg/w2HVcsQq

It was so iffy if it did it for me or not I just added it to my startup.. Get in the adjust throttle to where it needs to be then do the rest of the startup. Glad it worked out for you

its your setup. try setting back to 100%, redo virpil config and windows config. Either that or your mapping is off. to go from idle to off you can see the lever sticking out of the throttle. I have virpil and usually have to go from idle to off to get engine spooling then push up to idle

Turning off the G-Sync helped but it did not get rid of the issue. I think I did find out what caused it and it may help some others. I turned off Hardware-accelerated GPU scheduling in the Windows Graphics settings and it removed the stuttering when the game was in focus. Played a few missions and did a few full restarts and the stuttering never came back. To be clear the problem I had was when the game was in focus I had bad stuttering/ghosting but as soon as the game was out of focus the game ran great.

I need to keep testing more but I turned of g-sync on the set up g-sync tab and not just turning off v-sync on the manage 3d settings and it seemed to get rid of it. Will need to do more testing but work keeps getting in the way of proper testing.. need to send an email to my boss about work interfering with dcs time.

not sure what is causing it but I have a strange issue could use some help figuring out. I get bad stuttering in VR but only when the window is in focus and I move my head. I have the Pimax 8kx/3090 ect.. I tried Smarth Smoothing off and on. It is not bottlenecking as frames, ect.. all work great and the game runs great as long as I dont move my head but when I do I get bad suttering/ghosting and only in DCS even though frames stay the same. It works great when not in focus with no stuttering when looking around. Anyone have an idea of what to look at or run into this before?

Many of the bugs are issues with a persons install, not actual bugs, already been resolved, issues with ED and not the harrier, ect. Sure there are bugs listed trying to dig out useful information would be a waste of time.

Just give it time. I recently had to order the controller for mine and it spent from April 22 "Prepared for shipment from Russia" to June 16th Processing in the US with nothing in between. All in all, it took from April 17th to June 24th for shipping.

Well you see, it is called troubleshooting. By switching to IFA before start, it would eliminate all the things you do during startup if it crashed. If it didn't then we would try engines only, add some more of the process next time, ect.. trying to isolate it down until we find it crashes. Then once we find the magic sequence, have a few other people try it. This helps with the bug report and to help the programmers know there is a repeatable problem and how to exactly replicate it. It is a process of narrowing down the problem so you can actually see what the problem is. Right now there is no way to know is it a game bug or bad/corrupt file on your end, server or really anything. Going back to the original topic.. yes it is well worth half off. A lot of people fly all the time and sure there are some minor bugs but nothing show stopping. It is also missing some really cool features I hope we get, but again nothing show stopping. Razbam does need to do a better job telling people when they fix bugs as they do fix stuff that they do not mention such as recently fixing the volume know to 0 after takeoff bug. There are also quite a few bugs that are process so far down into the systems the most pilots will never see and/or they do not matter such as alignment. You should be flying coupled with the GPS in IFA as they do in the fleet from what I hear now and thus alignment entering and drift do not matter. It should be fixed but no way a show stopping or bug even most pilots will ever see.

Hey I think it is great.. needs a lot of work but good step.. Now I can use server comms and still be on a discord with my squadron. Beats SRS as even on the heavy SRS used servers still only 50% of the people actually use it. Maybe it will even stop some blue on blue as somehow it is a ground pounders fault they are not on the CAP channel to hear the raygun call. I now a lot of pilots who dont want to bother with SRS as this will be great for them and communication on the servers.

delete DCS World OpenBeta\Mods\aircraft\AV8BNA and then do a repair. If you need the syntax let me know. Also, remove any mods, non DCS store aircraft, ect... Then test and see if it is repeatable. What you have going on is not a bug. There is something else going on. The INS knob to IFA has been working ever since they put in INS without issues. Actually I just watched your startup. Flip to IFA before you do anything. See if that causes a crash. Also no reason to touch the efc, eng rpm or lids switch.

There is a very vocal percentage that consider the module very buggy. Most of the bugs that are complained about are very specific and limited or are user error. Bugs are also quite often getting fixed and you never hear it. Take it all with a grain of salt. There are quite a few people who fly this module constantly and it is very combat effective and great module.

did you flip the liquid cooling switch - rio - left wall? LIQ COOLING switch controlling the liquid cooling system for the AWG-9 and AIM-54. The AWG-9 circuit can be enabled independently of the AIM-54. This switch need to be enabled for the respective system before AWG-9 operation or AIM-54 missile preparation.

Your right, I do not code nor make missions but I do host a coop server for friends and the amount of issues we have are minimal. My point was that just because someone says there is an issue doesn't mean there is one. It seems the servers with the most scripting always seem to have the most issues. It is called cause and effect. Just because someone makes a mission, knows how to code doesn't make them an expert in a program where they have no clue how it is actually coded. I know server admins for weeks saying there was an issue with something in ED then week's later they find an issue with their scripting. I tell you what. If the server admins are so big on helping the community and wanting to make DCS a better place then have them publish their missions and code. Let other people take a look, maybe they will spot something they are missing. Let other people modify it and put up their own servers. How many do you think will actually release it? It would be a lot better for the community as according to them that is what they want. As for ED, they are releasing tons of updates. Sure there have been a few issues with them and sure there are some issues that need to be fixed but I would rather them work on verifiable, repeatable game bugs verse what some guy who thinks he know more than ED says.

I guess you didnt read the whole thing. I said there were issues in multiplayer. They even said they are working on some of the stuff. Face it, many of the items above is based upon a handful of servers with thousand of lines of scripting. To sit and think these all powerful server admins should have a direct line to ED, their input should be taken more than joe blow who just plays singleplayer just points to an entitlement mentality.

ED, Don't let all the griping get you down. You know what they say, it is always the 10-20% that scream the loudest. You all have been doing a great job. Sure there are a few issues in multiplayer, I know you all are working on. Strange though as long as I stay off of the the overly scripted servers, they magically disappear. I only get a strange issue once in a while then. People need to remember when you add thousands upon thousands of lines of scripting on top of a program when you have no real insight into the code it is bound to cause numerous issues. It seems you are expected to design your product based upon what 2 or 3 server admins want you to do with it. Then they hit you with the ego that their way is always right and yours is always wrong. Don't let it get you down and keep up the great work.

When you have time google how to change from steam to regular install. Really much better to run it that way than thru steam

The spawning is normal, try parking more towards the taxi way by the choppers. The mission is adding flights and will add them in the set parking places. Also I never stay on the ground. Land, taxi, ground power on, engines off, rearm - refuel, engines on, power off and go back up. Then orbit and just watch till clear. See if that helps.

A few things to try. Ensure it is working in windows. Control Panel > Devices and Printers > Throttle - HOTAS Warthog > rightclick Game Controllers > Find the Throttle and select properties and you should see one of the bars move. This will let you know if it is a physical issue or not. If that is good, it is probably just your axis settings in game. Go into the settings for the Axis and make sure nothing else is selected under any other controllers and ensure the right axis is selected under the throttle. Hope that helps a bit.. your gona love that stick.