RagnarDa

Dive bombing bugged? Yes! Fixed in next patch. All low-drag bomb modes are not working correctly. Edit: I meant low-drag

Yes easily seen in a mission with wind. The capsule steers into the wind.

I've checked and Viggen in DCS doesnt account for the wind drift of the submunitions. It may or may not do this IRL, the docs doesnt say. I anyway added this feature now, but it's impossible to make it perfectly accurate since the submunitions will be dispensed on different altitudes. Inputting incorrect wind-data into CK37 as suggested in this thread may not be a good workaround until the patch since it probably just introduces a error in the INS that just happens sometimes to coincide with the offset for the submunitions.

Many throttles (for example X52) has a low resolution so to be able to hit FTG at all the range was widened and made flat. A lot of work went into this.

So it’s an art-issue or it’s been implemented in the 3D model after this was coded.

Where are the developers? How would a bug tracker help with duplicate reports? Edit: and why is it a problem that issues are reported more than once? It’s not for me, actually it helps me gauge how many are affected.

The pilots manual says you are supposed to pull back on the stick when reversing, not forward.

Are there key binds for this or are this missing too?

Thanks for reporting and investigating the issue!

Agree a little annoying but also extremely trivial. Hopefully easy to fix, I believe end-users can do this themselves.

This sounds like a user error to me. Likely QFE. Happens for anyone else?

I might look into this eventually. Thanks for taking the time to make the report!

Thanks for reporting! Sounds like a reset issue.

Looks like a bug. Thanks for reporting. Should be easy to fix I hope. Meanwhile there is a workaround.

The thing is when I look into something is often the same time that I resolve the issue, if there is one to fix. Look at my post history. What I can do is as I said inform you that I’ve read the post, but that doesn’t mean that there is something for me to do. I don’t do this because I believe people will misunderstand. For example, there is a user error or the report is describing something that is so trivial that it might never be addressed. Nothing is perfect, especially not software so there will always be some issues. Even Doom still has bugs. Here’s one article describing how bugs are prioritized: https://www.mountaingoatsoftware.com/blog/defect-management-by-policy-a-fast-easy-approach-to-prioritizing-bug-fixes here’s another https://medium.com/@Zh0uzi/3-criteria-to-prioritize-bugs-53698bcda124 and yet another https://www.google.se/amp/s/usersnap.com/blog/prioritize-bugs/amp/

Where are the developers? Do you want me to write that I’ve read your posts? I read everything on the forums + hoggit. I spend on average about 1,5-2,5 hours each day on my dev machine but use my phone to read everything while on work (bathroom). I don’t have time to write in the bathroom and def can’t write anything informed. A informed reply takes at least 20 minutes, most often more time and I need access to my code/documentation.

I am here?

Here’s a track: Reconaissance mode? https://r.tapatalk.com/shareLink/topic?share_fid=74365&share_tid=216532&share_pid=4061382&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Fp%3D4061382&share_type=t&link_source=app I’ve discovered what I believe is the root to all the confusion surrounding reconnaissance mode, that the manual is missing the step where you select your M-point. You do this by setting SPA and AKTPOS and then the keypad key 1-9 (NOT B1-B9 but the keys you use to input coordinates and such). You can then transfer your recon-target to SKU by pressing SKU-button twice.

Ok added! Thanks guys!

Was able to reproduce the issue now. Probably related to me overzealously trying to fix the issue with TILS-light being on after you have landed. Fix in next patch probably. Thanks all!

Yeah that feature was removed a long while back. You can use third party tools to visualize the ELINT data.

Looks like the track doesnt show the mouse movement properly I guess but I press 1 on the keypad to select M1 as my destination, and then LS/SKU to transfer that to SKU-layer. Edit: I've just checked the manual and it looks like this part is omitted in the DCS manual. I'll notify JediTeo.

Wow! "What would undefined behavior of a almost 60 year old computer be?" <- This is possibly the nerdiest topic ever :D I haven't put super-much thought into this but I guess I at some time considered that CK37 possibly stored waypoints in a flat plane-system since it measures distances between points constantly, and latitude/longitude differ a lot considering where on earth you are. A flat plane cant be used in a too large area but Viggen wasn't supposed to fly much outside of sweden anyway. So I went with that and put the origo where the DCS map has its origo (so in Caucasus its on the Krim peninsula). Everywhere else where there is UB I would opt to go with what would be the C/C++ way of handling UBs. Please don't start to complain about this since it's well out of scope for the module. There is a lot of believable mismanagment representations already modeled in Viggen (for example I believe it's the first module where you could have a misaligned INS, and also the first/only where the gyroscope can be misaligned or drift).

I realized there is something here: If you try to select Bx-waypoint (or rather any special waypoint) without loading a data-cartridge or without previously defining that waypoint you'll hit undefined behavior. The CK37 will try load whatever is stored at that memory address. I've purposely kept these in as it is a realistic representation of the computer. It wouldn't load B8 as far as I can tell though. I've now added logic that will make sure that there are memory stored there that makes sense to the computer even though there is no data cartridge, I little less realistic maybe but for game-play reasons, just as the logic to place Bx8 in front of the aircraft when trying to make a fix when it hasn't been set before. Wasn't able to reproduce the issue in the post though. I did this: 1. Joined a random multiplayer server with Caucasus map 2. Started the aircraft as per normal startup routine 3. Inserted cartridge and set REFLOLA and IN 9099 LS when CK was ready 4. Out, AKT and Bx and then keypad 8 5. Set A1 and then T1 6. Fix appeared on radar straight in front of the aircraft, as expected. I'll need more info.

There actually has been a coded IFF-system in Viggen since before it was released. It was planned to be used with MiG-21 then when we where LNS. It was never integrated successfully in the MIG and the art-people hasn’t gotten around to animate the IFF-transponder yet so this feature in usage with AI has never been shown to anyone (even though it has worked without being visually there). Since then the feature has been removed since it first caused performance issues and then ED removed the parts of the SDK it relied on so it’s now dead. A very insignificant feature in Viggen if you ask me though :)