Ayabe

This has something to do with the placement of your monitors in Windows. I've had my setup going for a while but about a week ago made a small change to the graphics settings screen and from then on my entire screen was shifted up. I thought it was a viewport problem but none of that had changed - took me a couple hours to find these new settings and saw that my Y axis placement was -400, this is due to my use of a 1440p monitor in vertical mode, even though that is the one screen I do not use for DCS. That value comes from the difference in height between my 4K monitor in landscape and my 1440p being in portrait - along with that I run 3x external LCDs for MFD exports. It's an unusual setup for sure, but just in case this helps anyone else. If I had to guess as to a purpose - perhaps to streamline/simplify MFD exports and multi-monitor setups?

This is really the core issue and for whatever reason is more acute on the Viper. The Hornet is pretty easy to trim, same with the A10 and Tomcat.

Not sure how we could ask for much more than this - incredible experience improvements with little to no performance hit(potentially even better on some systems). Way to go ED.

If the Hornet still had no TGP sales would be pretty abysmal and a lot less people would be flying it. Most of use A2G utility would be gone unless you like typing coordinates all day. ED didn't introduce that as a favor to people, they did it to drive sales. So make it correct.

I had a heck of a time with crashes last night and finally pinned it down to the Mods\aircraft\FA-18C\Cockpit\Scripts\device_init.lua, I modded mine to use a diff kneeboard file to resize and move it. This file was updated to include something for the SLAM and maybe lighting and using the old version caused a crash. So anything dealing with device_init.lua will need to be re-applied to the new version. I did this for all my airframes just in case as it was quicker than comparing them all to my modded versions.

:thumbup:

Will do, thank you!

After patching and getting my fav. MP server I experienced two crashes that occurred at the exactly the same time. F18 takeoff from Novo, run mission, land, rearm/refuel, takeoff, run mission, touchdown and halfway down the runway hard crash. This happened twice in a row under the exact same circumstances, a few seconds after touchdown on the second sortie. I attached the logs for both. dcs.log-20200417-034759.zip dcs.log-20200417-031054.zip

The Harrier itself is fun to fly but for the A2G role the Hornet is far superior in a lot of scenarios. The only time I prefer to fly the Harrier is in "clean" airspace, free of sophisticated SAMs and redfor aircraft. HARMs are a lot better than Sidearms and I don't like having to rely on sneaking up on a Mig29 to have a chance. The Hornet TPOD is much easier to use even without being complete due to the Harrier slew being absolute nonsense and frustrating to use. TOO'ing GBUs is also a lot more work and prone to errors. You can't really pickle off several in one run due to having to laze-range every target. Perhaps once the Harrier CAS page is fully functional and you can pickle off 10-12 GBUs in one shot it'll be a real beast and have a leg up on the Hornet. The whole "click the map" thing to enter coords is so ridiculous it shouldn't even be implemented, just wait to do it properly. Harrier gunpod is great, basically a sniper rifle in A2G, it's very fun to use. As it stands I consider the Hornet to be the only aircraft in game that can survive and be effective regardless of the scenario for my play style. F-16 will get there eventually.

Uhh no, this is on ED to not be sending this sort of stuff out in the first place, it's not on the consumer to explain to AV companies why ED is sending out bad EXE's that exhibit the same behavoir as trojans.

Seconded, he's the best, clear, concise, no fluff and accurate.

This is the kind of stuff that just shouldn't happen, TOO transfers to PP has been "working" this way for almost 6 months, multiple tutorials have been written about how to use this - including Chuck's Guide and now 3+ weeks after ceasing to function you're trying to say that should have never worked? You couldn't reach out to anyone to let them know before people started crabbing about the functionality being totally hosed for the last 3-4 OB updates? Come on man.

I'm not sure why they just don't go full on Star Citizen at this point, there are enough sycophants to make it work, release some $5000 skin jobs and people will be bending over backwards to thank them. The deal I can't let go of is that ED has basically admitted that the the $70 or whatever each of us paid for the F-18 was never going to be enough money to complete the project and the only way for this to move forward is to keep shelling out for further projects - which also have no hope of ever being completed. So keep feeding the monkey or you get nothing.

I find the lack of any response whatsoever to this to be highly disappointing. This isn't a minor inconvenience and needs to be acknowledged and fixed.

It's ok to startup, fly around, fiddle with some of the systems, then land. Beyond that in any sort of combat scenario I've found it to be a frustrating experience. The showstoppers for me are the broken MFD exports where the contrast is too poor to really make anything out and the inability to edit waypoints. It's really bumming me out that the former isn't even really acknowledged as a bug, same as with the F18's fuzzy exports. I guess there are some LUA bandaids but I've yet to try them on the Viper.

As a semi-new player here are some basics I think would improve the overall experience and lessen the learning curve for new people. 1. Detailed in-game tool-tips for the various options - especially the graphics settings explaining exactly what each does and the possible impacts on performance. 2. Native support for customizing kneeboards, location, size, and composition. This should be built-in to the game and should work with any screen combination imaginable. Currently with a multi-monitor setup you're highly likely to encounter a completely unusable kneeboard without utilizing a third party tool like the Kneeboard Builder App(which doesn't work for some folks) or hacking up LUA's manually and then re-applying fixes after each update. 3. Much-much-much improved multi-monitor support in general. I know the focus is on VR but there is a significant portion of the player base who will never get into VR due to cost, physiological reasons, or just being generally averse to strapping a sensory depriving apparatus to their heads. You should be able to easily export any panel, gauge, screen, etc. on any aircraft to any monitor you want using a user-friendly interface built into the game. This should not require any external hacks or relying on hacks and then still ending up with a very compromised experience - like the thin HUD in the F18 due to the MFD's being blurry with the default settings. This also carries over to things like the training missions where the highlighted cockpit actions often don't scale properly when using multiple monitors which can cause some issues when trying to learn an new aircraft. While I'm pretty new to DCS World still, I'm not new to flight sims and spent several years living the dream in LOMAC before taking a break. Putting aside the steep learning curve of the modules(which is fun I think), it's really the time spent outside the game, digging through the forums trying to find that one post from 4 years ago where BlahBlahBlah details exactly how to fix X/Y/Z that quickly overwhelm a new player and discourage them right out of the gate. All of that time is a total waste and seriously detracts from the experience of the player - you really have to WANT to persevere and that's just not conducive to growing the DCS community. More flying, less LUA'ing, please.:pilotfly:

Will this ever be fixed? Hacking up LUA's and dealing with a crappy HUD are not a viable longterm workarounds. :cry: