Mayo2017

Chiming in with the same troubles. Drop on start with damage and gear extension following, unable to rearm/refuel, all of it. Wiped all configs such, removed all mods, ran a repair, installed VC++ as required, no luck.

Pages 22 and 23: Numbers from about #40-46 in the list point to the incorrect object on the cockpit diagram.

Bah, if you're trimming the tips of the grass with your air intakes, that just means you still have room to go lower. :music_whistling:

It doesn't help that (not sure about 1.5.4) what TrackIR says it's sending to DCS, and what DCS actually shows are different. For example, TrackIR will say that in-game I'm looking 60° to the right, but in DCS I'm actually looking 90° to the right. For me, things like E:D and FSX do exactly what TrackIR says it's doing, while DCS does not.

Could it also be the pitch/bank autopilot trying to pull the nose back up?

Yes. When entering coordinates in the PVI-800, precede positive coordinates with the 0/+ key, and negative coordinates with the 1/- key, negative coordinates being south and west. Currently, do not use coordinates taken from the ABRIS if you're in Nevada, since the longitude data is incorrect and will lead to bad waypoints. The coordinates shown on the ABRIS in Nevada are approximately 91km west of your actual position. See the map I added to the first post to help visualise the issue.

In Nevada, when programming waypoints into the PVI-800 for the first time in ages. Using the ABRIS to get coordinates for my waypoints, I input them in to the PVI-800 only to find that I was being told that I was some tens of kilometres off of my actual position. Cross-referencing my current coordinates as listed on the ABRIS, the PVI-800 SELF COORD and INIT POS, the F10 map, and my actual position on Google Earth, only the ABRIS was incorrect, consistently telling me I was about 1°1' west of my actual position. Issue is present across missions, both singleplayer and multiplayer. Issue is present in Nevada, is NOT present in the Caucasus. Edit: Attached map visualisation.

I've been using the limited ground attack capabilites of the Su-27 as a way to scratch that itch. Poorly-implemented as it is, using it like a Viggen is a surefire way to really piss some bad guys off when they aren't expecting something to come in at mach 1 at 20m AGL, dump rockets, and burn away. :lol:

This. It's already hurting squadrons that want to use new maps, but a few members can't justify spending the money.

Every second spent aiming is a second every unit beneath you spends aiming back at you.

Especially baffling when they've got a whole new engine to work with.

Hmm.... AS565 would sure be something.

Sorry, I meant to say "SPAK mode", I'd been awake for like 30 hours at the time. :D

Thanks for the explanations of the SA system! It was really bugging me not understanding what SPAK did, and it's great to know what the logic of the other modes is.

Just wanted to give a big thanks to the Swedes that corrected and expanded on my crappy cockpit diagrams. My Swedish is too poor to be of any help from here on out (and I spent hours hunting for some of those designations), so I'll just disappear and leave it to the pros. :D

Okay, so I took my garbage Swedish (and my wife is no help for the hard stuff inside a cockpit so I didn't even ask), and tried to give a general overview of the cockpit from the PDF posted a couple pages back. I made no efforts to hide where I wasn't sure, so expect question marks, notes, and mistakes. But it's a start, and I've got it all as PSDs, so correct any mistakes I've got and we're golden. I actually learned a ton about the plane in the process, and so you can probably see which pages I did first, and where I learned what things are.

You and my wife, good lord, I can't escape it. :megalol:

As long as I at least get the southwest corner of Finland, I'll die happy.

The possibility of a Viggen (which I love in its own right) leading to the possibility of a Baltic Sea map made me scream internally in sheer excitement at the mere idea.

I have a response, but I like not being banned. :lol: I guess we're just at the final "wait-and-see" stretch. Nothing more coming in the way of hints, I'd bet.

Having some nice, labelled reference images of the actual parts always makes it a treat. Thanks for that!

EDIT: I rebooted DCS yet again and... it all suddenly started working. Okay then. Not like I didn't try that before. So I'm working on a fictional livery, and I'm running into a couple aggravating issues that I'm apparently too much of a newbie to figure out. First off is the IR suppressors. The DDS file for the suppressors is in the folder, but the suppressors are always green no matter what. Second is the bort number issue in the middle of fuselage. Ugly green mess. No bort number entered in mission editor. Not sure where it's coming from. Here's the folder structure so I know I'm not going crazy. And the description.lua for good measure.

Screenshot would be infinitely helpful.

No problem inside DCS. You can set shift buttons inside DCS instead of the HOTAS software.