bigbear

Hello Miles! I pre-ordered the PointCTRL back on Feb 5, 2021. However, I still haven't received it or any notification that it was sent. I also wasn't assigned any tracking number, so I don't know where I stand in your order list. Do you have a record of my order? David Pratt Chesterbrook, PA Here is my confirmation email I received from you: -----Original Message----- From: PointCTRL <orders@pointctrl.com> To: david.pratt14@verizon.net Sent: Fri, Feb 5, 2021 5:59 pm Subject: Preorder Confirmation Thank you for Preordering PointCTRL. You will receive a PayPal invoice when your order is ready to ship. We are currently starting production for PointCTRL Version 2, and our goal is to have all preorders shipped within 60 days. Thank you again for your support and patience. The PointCTRL Team

I'm assuming that you went through all the various DCS threads here and videos on YouTube regarding graphics optimization. It turns out that I have a separate computer that I use to just run accounting software and my browser that runs dreadfully slow. Took it to my local dealer and he said that my Windows 10 is corrupted and that I need to reinstall it. Since that is something that is too much a pain in the butt because it means reinstalling all the applications, I just let it be (for now). There are YouTube videos on how to do a Windows 10 "repair in-place" without reinstalling apps or user data , but my system is so corrupted that I can't even run their repair utility. But keep in mind that Windows 10 can get corrupted and you may be able to run a repair-in-place.

Other things to consider: Check Task Manager to see if other programs are using significant CPU resources. Make sure any anti-virus programs aren't doing a scan in the background. Make sure any backup programs aren't running a backup in the background. Don't run DCS in windowed mode. Run DCS as administrator.

Also, DCS added a menu option to reduce stutter: Go to Options on your main DCS menu screen. Go to the Controls tab and click the "Disable hot plug" button at the bottom of the screen.

As a first step, make sure your system Settings | Gaming | Game Mode switch is Off. Certain other non-DCS software and upgrades can turn it on without you realizing it.

Lange_666, I see this discussion above regarding adding the following line to a "throttle section" of some Warthog HOTAS file: KeyAxis(&Throttle, THR_FC, 0, AXMAP2(LIST(0,37,42,77,82,100), VR_Zoom_Magnifier, 0, VR_Zoom, 0, PULSE+F1_Cockpit_view)); Please excuse my ignorance, but what is the pathname of the file you are referring to? btw: I am trying to solve the problem where the Zoom slider on my Warthog base isn't working in VR and I need some way to add that capability and I hope that this is what you guys are talking about. If not, if you could steer me in the right direction regarding this problem, I would sure appreciate it!

Just as an aside, be careful that you don't use TrackIR in a room with direct sunlight. The direct sunlight will interfere with the IR and your screen will go nuts causing you to think the TrackIR is defective.

Hi Wartooth. I too was having some major visual stuttering problems, especially with VR, but then found out one of the most important things to prevent it. Do this: Create a file in Notepad and name it autoexec.cfg. Place the following one line in the file: no_device_hotplug = true Place the file in the Program Files\Eagle Dynamics\DCS World (or DCS World OpenBeta)\Config folder. Restart DCS and the bulk of the stuttering will be over. Other guys play with adjusting things like shaders and so forth, but I now have excellent resolution and smoothness with Textures set at HIGH and Visibility at EXTREME and some other high settings. On the VR tab on the Settings screen, I set the pixel density at 1.2, though. I expect that the other settings that people recommend may be even better, but this is working great for me now. I can give you some other settings if you want, but I am not really an expert in this regard. I suspect that having lots of memory both on the 2080ti and motherboard makes a difference also, but I'm not really sure. Note that I am just running a 4Ghz machine without overclocking as well! I actually had to disable the overclocking because that was unstable in VR and was crashing my system. Maybe there are ways to overclock without going into "Gaming Mode", but I don't know how to do it. Gaming Mode is a disaster with this game in VR. I am pretty sure, though, having the 2080ti is a key to making this thing run well.

Well FoxxyTrotty, I tried their latest update, DCS World Vers: 2.5.6.45915, and the problem still hasn't been addressed. So I will continue to ignore the A10C module and focus on the WWII planes for now since the canned A10C missions are unplayable until that is fixed. As I mentioned, though, there are TWO problems that need fixing: the bomb accuracy and the bomb blast radius. Unless both are fixed, I can't trust that anything else is working right and I really have better things to do than be a DCS play-tester. For me, this is a real downer because this is the second time I upgraded my machine to play the A10C, only to find that certain software problems keep me from playing.

Nuts. I got the latest update full of fixes yesterday, but still no fix for the GBU38. Bummer.

GuiGon, as I was stating earlier, the GBU-38 is unreliable against soft targets as well. I was lucky enough to place one on the patrol in the second target, but even though it blew a hole in the ground not more than a couple of feet from a couple of soldiers, the soldiers just stood there like they were high on something. I just don't understand how some people can duplicate the problem and others cannot. I have a real problem accepting the idea that it is related to differences in hardware or quirks in system software. But I could be wrong. The fact is, the bomb radius problem was pointed out to E.D. four years ago. A member was able to point out the table in which you could adjust the radius factors (or some sort of factor that pertained to blast effectiveness) for each bomb with your text editor. That was a cop-out because then we had to go and research military bomb specs on-line to attempt to make up realistic numbers. It also meant that you could just go in and cheat with all the numbers to let yourself get through all the missions if you wanted. Regardless, my concern is also that there isn't a different radius based on the type of target, but I don't recall now the table or how it was set up and used. Evidently, E.D. hasn't worked on the issue ever since it began appearing back in World 1.5. I understand the need to keep revenues coming in by releasing more aircraft, but as our parents told us as children, "a job half done isn't done." It is sad because the A-10C was essentially their flagship module for years, and it still isn't right. And these modules aren't exactly cheap. I love what E.D. has done as far as the modeling of the aircraft -- even to the point of purchasing modules that I really didn't expect to play, just to help the company out. I think others have done that as well, even though I expect that most of us aren't part of the wealthy donor class. And sadly we don't get a deduction for our generosity at tax time. We all want E.D. to succeed in a BIG WAY. My concern is that they also have bitten on more than they can chew. I mean, just look at the entire idea of trying to effectively create a ground war campaign. If you really wanted to get any type of realism in that, you would actually need the latest Honeywell supercomputer to act as a server to handle not just the movement and battle results, but the AI as well. It is true that E.D. is seriously lacking in missions and campaigns, however, and I only hope they can find the right balance there. Learning the aircraft is fun (to some degree) and we all appreciate the beauty of it all, but ultimately, I think a whole lot of us find the real play value in the combat. I know that I sure do. I would really have appreciated a whole lot more having a campaign for the Battle of Britain than any ground war game -- using their existing aircraft modules and expanding on other aircraft that took part in that campaign. There are plenty of ground wargaming sims out there. In the meantime, we have serious problems in existing products. And in the case of the GBU-38, it has been outstanding for 4 years. That just isn't right. Not at all. That one thing corrupts the product so badly that I just don't even want to play A10C anymore. And that is a heart-breaker for those of us who invested in fancy hardware for it. That TM HOTAS itself isn't cheap.

No BigNewy. I'm afraid that you are mistaken. They are NOT generally on target. They are generally OFF target about 5/6 of the time or more. If you want, you can have one of your people log into my system and I can prove it. Or maybe I can provide videos of what I am doing if that would help -- which is something I haven't done but am willing to do if it will make the game playable again. You guys put in a lot of great work into this aircraft and to have it all thrown away because of ineffective ordinance calculations isn't good at all and I will gladly assist in helping resolve the issue. And doesn't the fact that the bombs are falling to the left and to the right of the target -- even when the SPI is taken DIRECTLY OVER the target followed by circling around again to perform the bombing suggest that it is NOT an elevation issue? If it was an elevation issue, wouldn't it mean that the bomb would fall BEHIND the target rather than to the left or right? And please also address the fact that the bomb radius calculations are totally screwed up as well for this bomb -- and perhaps others as well. I really hope this problem isn't lost in the process of resolving the accuracy problem. Again, I hope that you guys address the effectiveness of weapons soon. At the moment, I consider the provided A-10C missions unplayable and have moved on to the Spitfire which I hope won't have any of these issues due to the type of ordinance used at that time. The inability to use weapons on the A-10C just ruins the whole experience. Thanks -- and again, I am willing to help if I can.

BIGNEWY, please note that there are TWO issues here: One in which the bomb falls far, far wide of the target (meaning HUNDREDS of feet away to the LEFT or to the RIGHT) -- and that this is when you fly DIRECTLY OVER the target first to place the SPI -- meaning that it is highly unlikely to be an elevation issue, and secondly that the bomb explosion calculations are not making any sense. I mean a foot soldier can't have a 500 lb bomb explode DIRECTLY NEXT to him (and I mean the blast hole is no more than TWO STEPS from him) and not notice it! I have this feeling that there is a third issue where calculations don't account for the effect of a blast upon a soft target vs. a hard target. I remember prior to World vers. 1.5 that I could have placed a single GBU 38 either between the trucks in the first waypoint and destroy them both, or in the middle of the patrol at the next waypoint and destroy the whole patrol. Version 1.5 messed that up and due to the careful restriction of the limited initial loadout of weapons, you couldn't then finish the mission. It was shown by someone in the forums that the blast calculation table had been changed and he showed how to modify the table entry for that. But at least the GBU38 was landing accurately. I did some research on the blast radius of that bomb on the Internet and found that E.D.'s table entry was indeed no way near being realistic. I don't remember whether the table took into account the type of target. Now though, both blast and accuracy are messed up and I have no idea if blast radius is properly modeled for other bombs in the game(s). I know that the developers have a lot to keep them busy, but I genuinely hope that weapon effectiveness is high on the list for the simple reason that if your weapons don't work right, there really is no purpose to fly the missions. For me, it is enough of a downer that I don't even want to bother with the A-10C until E.D. works this out and goes through the missions CAREFULLY to ensure that they can be completed satisfactorily based on the loadouts given.

Thanks, BigNewY. Yes, as I mentioned, it is a problem in 2.5 as well. I hope ED can fix it soon. I really want to be able to play the missions.

Thanks for responding, ac5. Like I say, I am aware of the issue of the angle when trying to make the SPI, so I have even set the SPI by first flying over the target and placing the SPI when I am directly over it, and then circling around to approach the target again to release the bombs. No success. Note that if the problem was related to the wrong angle when taking the SPI, my understanding is that the bomb should have hit at some point beyond the target, not hundreds of yards to the left or the right of it. I need to qualify my results today, however. When I just started the program up again today, I was forced to update the 2.6.5 to the latest subversion. With that, instead of getting hits about 1/25 times, I am able to hit the target about 1/6 of the time. Maybe ED made a slight fix, but it wasn't good enough I'm afraid. I am getting pretty fed up with the A10-C. Maybe I should give this up and go to the Spitfire until they can straighten out their weapons for the A10-C.