phantomknight321

I remain hopeful that there will be a fix in the update today (I haven't checked, I am just assuming the update is still scheduled to release today) patch delayed until tomorrow, but I remain hopeful

This thread has me thinking the sweet spot from my 1080ti may be a used RTX 2080ti (If I can find one for less than 600) or the 3080. I just recently got my 1080ti a couple weeks back and while I am happy with the performance bump from the 1080 I upgraded from, I still seek more. Though, it doesn't really seem going with a better GPU will even get me the smooth experience I am seeking.

Another thing that can help is dropping more than one bomb in a pass. Kind of painful to do when you have limited stores, but by doing so it helps you have better chances of at least one of them hitting

Bringing this one forward. I just picked up the H420 and the custom drivers do seem to work with it, but the pen inputs are not detected whatsoever. I get the same strange device manager behaviors Echo179 got. As seen in the log files, it does detect the tablet using custom drivers: 2020-05-21 16:52:53,534 [1] INFO VRKneeboardLib.UcLogicDevice - Custom driver 2020-05-21 16:52:53,575 [1] INFO VRKneeboardLib.UcLogicDevice - Custom driver detected VID:256C PID:006E Device:Huion Something is not talking, and i have spent the entire day with the awesome and patient discord users trying to sort this out with no avail. I am determined to make this thing work one way or another! For the other poster that got the H420, did you ever get it working?

Somewhat off topic, but does your team still plan to someday become an ED partner and develop as a third party to sell your modules? I would love to see your next big project become an official release!

Hello, I noticed when attempting to bind the Antenna elevation and range axis knobs, I am getting some strange and frustrating behavior. Expected Behavior: Turning knob moves antenna knob or range knob to a point depending on knob position. Actual Behavior: Turning knob up or down increases the rate of change up or down, and moving it back to center makes it stop moving, rather than re-centering the axis. I will try and get a video of this behavior later, but is this actually correct? Anyone else having this problem? I vaguely remember this being an issue on the hornet, but haven't followed up to see what happened with it, and I haven't been using the axis anyway.

This sounds fantastic! In the same boat, cant really afford to pick up the tomcat and blew what I could on the viper because I HAD to have it, but someday I hope to grab the cat and experience it. Anyway, I think multicrew is fast becoming a hot feature in DCS. Not every jet needs it, but those that do seem to be pretty popular now. Moving on, I threw a thread out there asking about the viability of maybe a block 52 variant...same year and capabilities...I just like the idea of having the variety to choose different engines essentially

I know we are getting the Block 50 2007 F-16CM, but what are the chances we could also get the Block 52 of the same rough capabilities? Only main difference would be a different engine model, would be neat to have the choice of the two different F-16 engines. Probably a long shot, but I figured I would throw it out there anyway, maybe itll be something that can be considered in the future!

Just throwing my .02 in; for sure, i think the right direction would be bringing out older variants in the future, or maybe more unique variants with different capabilities. They could either sell them as standalone modules, upgrades to the owners of the viper we are getting, or maybe it could be both, so someone who does not have the f-16 in the future can pick which one they want, then add on the other variant later. I also agree on getting 2 seater variants, I haven't tried multicrew yet but on paper it sounds amazing, and I like the idea of having the opportunity to try it in other aircraft down the line

Not a huge loss; i typically find myself completely disabling the moving map generally, its so bright and clutters up my display. Only times i find it handy are when I am double checking an airfield I am landing at...but otherwise it gets turned off ASAP. Instead, I try and just use visual references, waypoints, and the kneeboard

Lots of great things that got touched on in here; I really appreciate the level-headedness that usually tends to prevail on these forums and the discord servers lately (probably due in part to ninelines hard work in maintaining order) I DO believe that part of the outrage around the viper in particular was solely coming off the heels of the carrier controversy. While the issues will probably have still come up, the community was already worked up from one thing, so it was easy to scrutinize the next. That being said, I think that the approaches being taken thus far are great. Allowing for the LAU-88, fantastic. Even if it doesn't happen in the end, I appreciate the effort to allow for flexibility in loadout (and I would be lying if I said I would never use it, despite being a strong defender of EDs choice to exclude it before). Any other outrage the community wants to get into over other things, like JSOW and Sniper stuff, people just need to remember that this is military hardware getting simulated, there is only so much ED can do, and I am positive they will do their best to give us the most that they can.

Good Afternoon, I noticed this quite a while back, but it was recently brought up on reddit and it has reminded me to bring up a bug report about it. Currently, the SUU-25 launchers do not perform correctly. Here are some notes from a reddit user that better explains some of the strange behavior: “...I've played a bit with it with limited success. If you select them on the Stores page and pickle, nothing will happen, BUT if you click on the delivery method button (the one on the left, where you get the CCIP/CCRP/AUTO for other weapons, mouse only, HOTAS button doesn't seem to work for this weapon) they'll all suddenly release. All of them. Which is a shame because your AFAC load goes from being capable of providing 45 minutes of illumination (170sec per flare * 8 flares per pylon * 2 pylons) to just under three minutes.” Thanks in advance for checking into this! Sent from my iPhone using Tapatalk

I’d be ok if this was a special options setting for the a10 and hornet, I think that would be the ideal way to handle things. That said, I don’t mind things as they are for now. Sent from my iPad using Tapatalk

Excellent! You are doing fantastic work, keep it up!

I know this is an old reply but did you ever figure out what was happening? If not, I think already know what it is; by design, Harriers take off in the air from land no matter what due to the AI being buggy, even if you don't have any AI wingman. I think it is the same for the carriers too. OP might've fixed that and I missed it though