RagnarDa

Which might already have been fixed :)

Are you sure you’ve set-up your controls correctly? Maybe try using the keyboard-controls or deleting the input-settings in your saved-games folder. Also, make sure you don’t touch the emergency trim controls as this will block the normal trim.

Yeah I should have mentioned this would assume you also started “fresh” when you first recorded the flight. If this doesn’t work I’ll have to see if there is still some randomness that I’ve missed.

Repair and Watch track The fix with removing random numbers has already been released. It is possible that I missed some but I don’t think so. The problem was that since a little randomness was introduced the outcome would not be the same when you play it once and then replay it. Another long standing issue is though that the state of the aircraft is not 100% reset when you spawn so it could happen that for example if you start and toggle a switch and then restarted the switch would be in the position you had when you restarted. This also affects replays. I have been hunting these kind of issues for a while and it is difficult to find every single one so there might always be some left. I did find some that has been fixed in the upcoming release though. If this is the reason replays are off you could try restarting DCS and running the replay without doing anything in between. About repair not working: it’s my number 2 or 3 of things to look into right now.

:)

If it's not in the next update it will be in the one after that.

Found the problem! I learn something new everyday, like if checking between a unsigned int and a negative int is always true in C++!

Fixed!

I believe I've found the problem and implemented a fix.

We have been looking into this and it’s difficult figuring out the best approach. One problem is that neither me nor Cobra actually see any degraded performance on our machines, but we do kind of have powerful computers. Cobra tried swapping out the cockpit for Su-25 and didn’t see any improvement. I did a profiling analysis of the code and Viggen FM and avionics account for 2-3 percent of total CPU-time in DCS according to the analysis. I did notice that my FPS seemed to improve when going to external view so I tried turning off all the displays in Viggen (which it has a lot of: HUD, waypoint indicator, data indicator, radar, kneeboard) and at first I did see ~5 FPS improvement but when I tried it again it didn’t show any improvement. There are definitely areas that could be improved code-wise but it is difficult to tell if it would have any measurable effect at all. I’ll update you if I find anything.

You are in PLAN (plane/level)-mode and not precision-mode. If you'd pulled up so you kept the sight on the target you would have overflown the target at precisely the correct safety-height (I think 400 meters). That's at least how its supposed to work.

Hey I write here but this relates to https://forums.eagle.ru/showthread.php?t=203864 and https://forums.eagle.ru/showthread.php?t=184496 as well as rocket-sight inaccuracies too. I've spent the last 1-2 months trying to figure out how the sights are all inaccurate all of a sudden. Among things I've discovered is that the radar-measurement was calculated wrong and other smallish things, I've also found that ED changed their atmospheric model at one point (which I knew but choose to ignore in hopes the problem would go away). Anyway, the newest member of the dev-team Grover managed to make a new fit for the barometric altitude calculation so the calculations is again close enough. This effects pretty much all weapons in the Viggen. You can tell if the altitude calculation is off in the sight-modes that have the MålUtpekningsSymbol (MUS, I think its called Target Indication Ring in the english manual) if the ring appears either under ground or floating above the ground. The fixes is going through the hoops right now... Btw, thanks for the video! They do illustrate it very nicely!

Yes please! I was able to replicate it on my machine at one time but never again. I think it is sufficient with the small piece above, cause it looks like the “held” event is dropped somehow. IIRC I read somewhere a similar issue in the Mirage.

Yes, Rb15 do left or right turn in terminal phase IRL.

I assume those are Rb-04 (for AI) fired by AI airplanes? If so they do that because that’s the standard behavior of anti-ship missiles in DCS. Rb04 fired by a player airplane won’t do that because it has custom behavior, it would work as the real Rb04 then.

Hey it looks like it is bugged in some way. The way it’s supposed to work is you input the heading from the pop-up point to the target, so inputting 090 should make it so your plane comes from west of the target. At one point previously IIRC there was a mixup of clockwise and counterclockwise in the pop-up input (DCS uses counterclockwise directions internally), so it would be correct at 0 degree and 180 degree but 180 degree wrong on 90 and 270 degrees. I think I’ve fixed that since, but had other reports of for example the distance being wrong. Can’t figure out how it could be wrong in the way posted by the OP but it’ll check (when I have 5+ min for development).

RB-15F usage in 2.5 beta There are two ways to fire the Rb15: (1) when fireing in ANF-mode it will use the waypoints as programmed into the computer (you can still update the position of Bx8 etc using the radar but the position of the target should still be somewhat known ahead of time), and (2) when firing in NAV-mode it will be more of a target-of-opportunity situation a where that Rb15 will fly straight ahead and target the first ship it sees. Edit: Viggen is meant to be used in pre-planned strikes. Also, carrying the Rb15 (and Bk90) was not part of the original design and more of a interim-solution until Gripen was available and it wasn’t able to use all of the features of either weapon systems and the interfacing was kind of shoe-horned into the existing interface.

Hey sorry for late response. From what I remember I think you need to set Bx8 (and Bx6, 7 and 9) using coordinates entered into the computer. From what I remember we considered creating an fictional mode where the cross would appear in front of the aircraft if you hadn’t entered a latitude/longitude for Bx8 but I don’t remember if we ever did (this would then not entirely follow how it works IRL but would be easier for player to understand). If you would help me I’d like you to program Bx6 through Bx9 by entering the coordinates in the computer and see if that works for you.

Here’s a video of how to select a cartridge: Sharing Pre-flight Planning concept https://r.tapatalk.com/shareLink?share_fid=74365&share_tid=195685&share_pid=3300927&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Fp%3D3300927&share_type=t You should however select #7 instead. Let me know if it works for you.

There is a key-binding (I don’t remember the name) which you select which cartridge to load. If you have the relevant kneeboard page up you will see which one you have selected (starts with 0, press once for 1, and then 2... etc). Cartridge #1-5 are the ones in the init.lua-file and #6 is the auto-generated one, and finally #7 should be the one you have in your saved games folder. Sorry this is a bit rudimentary at the moment.

Minus sign on CK37 display? I did have a look a while ago and wasn’t able to fix it. Couldn’t figure out what was wrong so I just resigned to keeping the 9 as a fallback solution. Maybe possibly Jediteo can fix it, it’s a lua/texture issue.

Btw could you be a little more specific about what issue you are talking about mbot?

I tried but didn’t get it to work any better than it already does. Not sure what to do yet.

I am currently looking into making an option to disable the collimation effect of that display for users that don’t have Track-IR (and also people having issues with it using VR). Currently the only sulotion is to use snap-view for users without head tracking unfortunately.

Do you have easy avionics on?