Snappy

Also at about the 3:00 point in your video you are flying straight through the tacan radial that you were supposed to intercept and instead you keep flying straight ahead further and further off-course. When the HSI needle approaches the Center of the HSI you should turn left (take heading 089 for starters and adjust from there ) and fly outbound on that radial 089 (so keep the needle centered) . I don’t understand why you are changing the HSI course again afterwards, you shouldn’t do that.Recommend you re-read Zabuzards post and watch the IFR training video he posted again.He explained it pretty well. Dont take this the wrong way, but I think you haven’t fully understood the basic IFR navigation concept yet.

Given EDs huge developement backlog and the amount of stuff that was supposed to be out by now according to ED themselves (Vulkan 2024 anyone? GFM to come in 2022..etc etc ) I dont care much anymore for what they tease. I would go for more delivering and less teasing /hyping. And seriously prefer Nick Grey not doing the "passion and support" talk bit again .It is a bit tone-deaf and ill fitting by now.

I don’t doubt it’s possible to do it technically , but I also think there are reasons why the real world manual explicitly says use the pedals. Probably amongst other things because at low speeds you get no response, since stick movement does not actuate nosewheel steering contrary to the pedals, and the rudder is not effective at low speeds because of insufficient airflow. And in the opposite way using stick to control yaw during take off roll gives you uneven lift and drag distribution because the elevons deflect which is also not desirable.

A few more things to consider: A) The AJS 37 is not a dedicated air to air platform, unlike the F-15. B) The F-15,16,18 and Mirage you came from, where all designed with a high amount of manouverability and high thrust to weight ratio. C) In regards to the GS video, the video is from 3 years ago and I think there was a significant revision of the Viggen flight model in the meantime if I remember correctly, because it originally performed to well. Doesn't mean you can't fly air to air with the Viggen, it isn't too bad actually, you just need to be aware of its limitations and where the strength and weaknesses lie. It fares better against contemporary aircraft of its era. Unfortunately the AI Mig-21 is not very realistic in its flight model and overperforming a lot ,last time I checked.

Not sure where you got this idea from. The real manual says to use the pedals. If you want to look it up, its in the AJS 37 DEL 2 Kap II manual, page 17 in the manual (page 23 of the pdf) where the take-off procedure is outlined. Clearly says after brake release "Styr med pedalerna."

Hi, previously it was possible during approach phase when you put the optical sight into approach mode to display the FPV on the sight , that you could dim the gunsight reticle with the MOVING AND TARGET RETICLES INTENSITY RHEOSTAT , so it doesnt interfere/block your clear view through the sight during approach. Now this is not possible anymore, because when you dim the gunsight reticle, the FPV also gets dimmed simulteanously. So if you make the gunsight reticle insivible with the rheostat, you also lose the FPV indication. Was this an intentional change, because the previous behaviour was incorrect?Or an inadvertent bug? Short track attched showing the behaviour on the ground in take off position. Kind regards, Snappy ReticleFPV.trk

Wow, thank you very much for your detailed and quick reply Renhaxue! Especially for giving english translations to the different sub chapters, very helpful. This clears it up a lot for me! Much appreciated. Wish you a nice weekend! Snappy

Yes, otherwise you wouldnt see the zero degree center marking for scan elevation at the top of the radar screen in my picture. The center marking shows upon selecting air-to-air mode, but the +/- 10 degree markings don't.

Hi @TOViper I know you recently reworked the page about the A2/B-scope in Decembre last year , however I would like to add a few suggestions to the current version: This is from the current 18th Oct 2024 edition: The B-scope is used when additional detail is needed. It displays a vertical extent about the range of a selected waypoint from -6 km (near side) to +4 km (far side), and ±20° horizontally. This view takes the distance to a selected waypoint (left picture), and places the near and far borders accordingly, but it doesn't attempt to scan the waypoint itself. The mode just scans at the same range to the selected waypoint, no matter if this waypoint is in front or behind the aircraft. A couple of things: - we may be splitting hairs here, but the near and far limits are 6,5 and 3,5 km respectively -I would rephrase the 2nd part of the paragraph here: This view takes the distance to a selected waypoint (left picture), and places the near and far borders accordingly, but it doesn't attempt to scan the waypoint itself.. I understand what you try to say and it is somewhat clear, but it could be worded differently and slightly more accurately . I would suggest: The A2 / B-scope mode is used to provide additional detail of a specific area. It displays a vertical extent about the range of a selected waypoint from -6.5km (near side) to +3.5 km (far side), and ±20° horizontally It is important to note that this enlarged view of the area is not anchored to the actual waypoint itself, the radar only takes the distance to the selected waypoint for reference and shows an enlarged view of the area currently ahead of the aircraft at that distance with the following borders : -6.5 to +3.5 km distance to selected waypoint and -/+20 degrees left/right of the current aircraft heading. Whether or not the selected waypoint itself is located within that area or not is not relevant for the radar scan orientation in A2 mode. It scans ahead of the aircraft within the above-mentioned limits , regardless of the actual selected waypoint location being to the left/right of that area or even behind the aircraft. I would also definetely add that the radar picture in A2 mode is compensated for speed and doesn't "move" with the aircraft but stays "in place" Something like this: The enlarged area view shown in A2 mode is automatically compensated for aircraft speed , so the radar picture does not "move along" as the aircraft moves. In other words the radar scans and shows the same geographical area (unless you change aircraft heading) while the aircraft is flying towards that area. This compensation for aircraft speed ceases when the aircraft approaches: 0.6 km range to the "bottom" limit of the scanned area when radar range is set to 15km 1.2 km range to the "bottom" limit of the scanned area when radar range is set to 30km 2.4 km range to the "bottom" limit of the scanned area when radar range is set to 60km 4.8 km range to the "bottom" limit of the scanned area when radar range is set to 120km At these limits , the radar picture begins to get blanked from the bottom of the screen upwards. However its just my suggestion and personal opinion. I attach the relevant page from the AJ37 Del 2 Kap 1 manual: Thank you for your continued hard work on improving the manual, Kind regards, Snappy

Currently the radar in air to air mode doesnt show the +/- 10 degree markings for the scan elevation: For reference, picture from the Del 2 Kap 1 manual: null Kind regards, Snappy

Hi @renhanxue, I'm trying to slowly work my way through the real world manuals, as a non swedish speaking person, its a bit difficult and I have a few basic questions regarding the manuals general structure and availability. I hope you can maybe answer them shortly. The Del 1 Kap includes the following general manuals overview at the beginning(red by me): nullI'm a little bit confused, so my questions: (speaking about the AJS37 manuals only, not the other ones for AJSH37 or AFJF37.) 1.) Why does the overview here say that Del 2 consists of Kap II-VI only, when there is also a Del 2 Kap I which deals with SI and Radar? 2.) the Del 4, did it ever get declassified or become available? Do you know what it deals with approximately? 3.) As a very crude summary is it to correct to say the manuals can be divided into this: Del 1 Kap I = general introduction and aircraft description Del 2Kap I = SI & radar description and assorted attack procedures Del 2Kap II-VI = procedures, limitations, performance Del 3 Kap 1 =Performance graphs. Thank you very much! Kind regards, Snappy

sorry but these roadmaps are basically useless PR stunts and the information in them cannot be trusted anymore . They are off by years at best. Its pretty obvious that either ED is either overwhelmed by the development backlog or simply keeps seriously overestimating their own capabilities.Or both. To give just a few examples: by their own words, they estimated to release MAC (which is now dead) latest Q4 2021. And that was already years after the original 2018 (if I remember correctly) announcement trailer. Source : https://www.digitalcombatsimulator.com/en/news/newsletters/d5bb893019c9a8c047d07a678b211c55/ Another example: The improved GFM flight model for AI. ED expected implementation for fixed-wing AI aircraft in 2022. Now we have almost 2025 and there has been almost zero information anymore on the subject at all. Source:: https://www.digitalcombatsimulator.com/en/news/2021-12-03/ Lets not get into how many other things were supposedly just around the corner and never materialised so far. OP has a valid point but sadly I doubt an interview with Nick would bring anything but more of the marketing speak that I lost trust in long ago in DCS context.

If it helps, I like you though

Yea I saw, he must like you or maybe you have the magic touch TOViper pinged him twice in that very thread , in Aug and Oct and both times he times he never replied. Still , let’s see when and if we get an actual bugfix. But thanks for the heads-up!

„Although SFM produces accurate trajectory parameters such as turn rate, specific excess power, flight envelope“ At this point, I don’t buy this claim anymore. ED has shown time and again how they like to put out marketing hyperbole, while actual in-game state is nowhere near that. (SFM). This has not changed and defines a more data-driven means of achieving flight dynamics, in conjunction with some scripting. SFM was used in the Lock On series and is still used for AI aircraft. ..Some scripting..right. People have shown that the AI is able to pull more G at lower speeds and higher alts than player in the same aircraft.And not just a few percent because they fly a supposedly „perfect“ technique. If the AI used the same lift drag thrust and weight and AOA limitations as the player this wouldn’t be possible. The FAQ bold you quoted clearly says SFM was used for player aircraft in LockOn times.That’s ages ago.The LockOn aircraft were much less realistic and simplified in their performance. One flight in the DCS MiG -29 should show you that the flight model is far from the LockOn Variant. Besides, many of the overperforming AI aircraft in DCS didn’t even exist back in LockOn days.There was no player flyable F-5 ,Mig-21 and Mig-15 just to name a few. Anyway I’m out of here now, I can see this is going nowhere.Keep believing what you want.

Not sure , what point you are trying to make. I already told you AI fly on SFM . You were the one originally claiming AI used exactly the same model as player aircraft. Which is untrue. Player aircraft nowadays use AFM or PFM, or EFM. Not SFM since a long time. Maybe during LOMAC days or early Flaming Cliffs. However not anymore: https://www.digitalcombatsimulator.com/en/support/faq/general/ These AFM/PFM/EFM models are far apart in complexity from SFM.So AI does in fact NOT use the same flight model as player.Contrary to what you said.

The current manual 2.1. says on page 312 , about the Radar release and Radar NAV bombing: On weapons release, the radar is set to A0 automatically. This doesn't happen in the DCS Viggen. I flew attacks both in radar A1 and A2 mode. Neither with Radar release RR nor in Radar NAV attack did the radar go into A0 mode after the FÄLLD LAST light comes on. I attached track files and mission files used. (I know in the attached tracks I stayed trigger unsafe after release, but I flew another attack testing if going trigger safe after release influences the issue , it does not. The radar does not go into A0 automatically anyway) M07 - SB71 LD RR RADAR.miz M08 - SB71 LD RR NAV.miz RRattack.trk RNAVattack.trk

Hi, I found a bug in the radar display. As far as I understand the manual, with any of the 3 possible air to air modes selected on the the weapons selector ( LUFT/RR , AKAN JAKT and IR RB) , the radar scan elevation should be shown on top of the radar display. For AKAN JAKT AND IR RB , this work consistently. For LUFT/RR is doesnt. It seems to wrongly depend on the direction of the selection on the weapons selector: If you go from RB75/MARK/DYK into the LUFT/RR selection , the radar does not show the scan elevation in LUFT/RR mode. However in the opposite direction, if you go from AKAN JAKT to LUFT/RR on the weapons selector , the radar correctly displays scan elevation on top for LUFT/RR mode. I attached a short track , illustrating the issue, as well as the mission file. -------------------------------------------------------------------------------------------------------------------------------------------- Separate , but related question: The current release manual 2.1. says the following about radar air to air mode (p.351) : The air-to-air mode is selected by setting the weapons selector to any of the air-to-air weapon positions: RB05 LUFT (RB05 A/A), AKAN JAKT (gunpods A/A), or IR-RB (IR missile) and then setting the radar mode to either A1 (PPI) or A2 (B-scope). The elevation of the radar is centered to +1.5° relative to the horizon and can be manually elevated using the radar elevation knob. In the air-to-air mode, the antenna elevation indicator is added to the top part of the radar scope indicating the elevation of the beam relative to the 1.5° center. It says that the radar scan elevation indicator is added the radar display upon selection of air-to-air modes. The first paragraph mentions air to air mode can be entered in A1 and A2. However DCS currently in A2 mode , you don't get the scan elevation indication on the radar display in any air-to-air mode at all. Only in A1 mode. Is this correct and the limitation to A1 mode is simply not mentioned in the manual (yet)? Or should the scan elevation also be shown in A2 mode and its another bug? Kind regards, Snappy ScanE.trk ViggenAir2Air.miz

What about the much anticipated AI GFM flight model.? According to your own newsletter you expected implementation in 2022: https://www.digitalcombatsimulator.com/en/news/2021-12-03/ Now we have 2024 and have heard basically zero anymore about it , never mind having an actual implementation for fixed wing AI. Unrealistic overperforming AI flight models is one of biggest game and immersion breaking issues with DCS.

This statement is plain wrong , sorry . AI uses a simplified SFM , which often results in unrealistic performance. That was supposed to be changed by implementing a new , more accurate AI flight model called GFM , but this seems to take ED longer than expected. It’s been a project since at least 2021 and so far not single AI fixed-wing aircraft has received GFM in-game , at least not in the customer releases versions we have.Supposedly the helicopters use it. ED showed a demo video of the AI MiG-29 with GFM but that’s it.Implementation was slated for 2022. Now we have 2024, but that’s typically ED for you. Dont need to take my word for it. Here straight from the horses mouth. Read especially the first and second paragraph, it makes clear that the AI does not use the player aircraft AFM/PFM as it would impact computational performance too heavily. https://www.digitalcombatsimulator.com/en/news/2021-12-03/

Not quite, the autopilot steered-Oerlikon 30 mm gun is very unique for the JA and would be a first in DCS too.

Ah, very good! Thanks for the info! I just noticed another unrelated bug though , which I hadn't realised before: During landing phase 1 on a normal full approach,once you select LANDN NAV , the active waypoint is correctly set as LB1, however I notice the waypoint distance readout is showing distance to LF/the destination airport) I dont think this is correct. Also,on a seperate note, the go-around functionality described in the manual is still not working at all . If you are in phase 2/3 and turn more than 90 degrees away from final approach course, the active waypoint should automatically switch back to LB for a new approach. In DCS it doesn't. This is what I meant in my post, unfortunately the approach system logic at the moment looks like it needs a big overhaul. So as far I understand it as a quick approach system summary, there a 5 bugs there. 1. the wrong HUD guidance to the parallel final course (original topic of this thread) 2. During Approach phase I with LB being the active waypoint , the yellow course index on CI wrongly points to LF instead 3.During approach phase I with LB being the active waypoint, the waypoint distance readout dial instead shows distance to LF (may be related to above bug no2.) 4. After manually entering approach phase II via flip flop, the active waypoint is initially still wrongly shown as LB, it should actually switch to LF. 5. automatic go-around functionality not working at all ( turning more than 90 degrees away from final approach course during phase II/III doesn't prompt automatic switching of active waypoint back to LB for a new approach like it should. Manual Go-around function also doesnt work ,you should be able to trigger it by switching mode selector to NAV and then back to LANDN NAV , to set LB as active waypoint. If you do it, it just switches back wrongly to LF as active waypoint

Very nice . At least I'm not going mad. I just tried another thing and now I think its not necessarily related to short approaches, but either the HUD guidance for approach in general is buggy or its something related to TILS interferrence. I flew the attached night mission from the same training mission pack ( you are set up at the same spot, southeast of Kolhki). This time I flew the full approach several times, just selected LANDN NAV and followed the HUD guidance to LB. The same thing seems to happen on a full approach there . Before reaching LB, the guidance goes to the left to parallel course and after a short while ( which seems not always the same. sometimes it notices pretty fast ) it catches the error. Also, another question: During approach slightly after point 5, after the HUD catches its error , when the CI no longer shows the final approach intercept circle radius, but instead puts the circle on the destination airport with the centreline extending from it. Do you also see this glitch on your CI that the runway centerline indication seems to be sometimes either flashing or not visible at all? Heres a picture I took, when the line was flashing. Right now the line is not there at all, but it should be where I put the red line: M08 - Landing - Dark.miz

Good Morning to you too Viper! there is actually another 3rd bug in here, which I had also already reported long ago , thread link below. You can see it in my section 4 picture : After I shortened the approach via Flip Flop, the destination waypoint is still shown as LB1 , this is wrong according to the manual. By shortening the approach/flip flopping, I manually started approach Phase 2, during this phase the destination Waypoint should be LF . (Phase 2 can be entered either manually via shortening approach , or automatically during normal approach by overflying LB point)

Hi @TOViper, I tested this again today, and the issue is still present. To be honest , currently I find the whole approach phase pretty inconsistently modelled (the HUD guidance and yellow CI course pointer are wrongly leading to different directions most of the time, not matching the manual description) Can you please try to refly the following attached mission? (Its from the older Viggen training mission pack from the user files library by cornivus. This mission sets up you up airborne about 20 nautical miles southeast of Senakhi for a landing in westerly direction on runway 27. I did the following, immediately after mission start,: 1. I selected ALT hold (I didnt want to land, just check HUD lateral guidance). 2.I selected LANDN NAV , You can see the HUD guidance is correctly, slightly to the right to the curved LB final approach course intercept (but the yellow CI course index pointer wrongly points to LF, despite LB1 being the current destination waypoint , this is another separate bug, CI should only point to LF when Landing Phase 2 begins, which is AFTER passing LB) null 3. Immediately afterwards I did the flip flop LANDN NAV/ PO / LANDN NAV: ( the system correctly shortens the approach and provides guidance to the left to the new shortened final approach intercept course intercept) 4. On the way to the shortened final approach course intercept, everything seems correct. 5. Before actually reaching the intercept point to final, the HUD suddenly again starts guiding to the left (the bug I originally reported) ( you can see the HUD turns me left, parallel to the approach course, and as you can see on the CI, where the extended centerline is drawn to my right , the nav system itself knows where he airport is , so its not a navigation accuracy error it seems , the HUD guidance itself is wrong. Interestingly , shortly afterwards , almost as soon as I roll out on the parallel heading the HUD seems to realise its error and jumps far to the right, to guide to the actual airport, but unfortunately by now the approach is a mess and the new guidance seems to the airport itself and not an actual intercept to final approach course... Sometimes the HUD seems to catch its own error earlier, while you are still in the turn to the parallel course. But I've flown this multiple times now and never did the HUD once guide correctly a contineous smooth intercept to the shortened final approach course. Could you kindly refly this mission on your computer and follow my sequence exactly? Its important that you start the LANDN NAV mode and Flip Flop immediately and that you also follow any change in HUD guidance immediately and just stupidly fly following the HUD , ignore the yellow course pointer on the CI. Sorry for the low quality screen shots, I dont know why the pictures became so low res during forum upload. The originals are much sharper, but you can view them if you click on the pictures. Kind regards, Snappy M06 - Landing - Clear Sky.miz