104th_Cobra

Scan Sector, not working confirmation on updated DCS Openbeta. On log: Unrecognized : 'scan sector'

I don't want to ruin the party which is claiming that ground radar capabilities are pointless, but it's ridiculous seeing the use of IR TPODs on adverse weather, when the sensor is an optical passive one. Fog, clouds and mostly rain will degrade or prevent the use of guided weapons wich depend on previous optical passive acquisition. Until the 90s, before GNSS (GPS), the pratical option you had for a capable and accurate weapons delivery on adverse weather was to use one IP for INS update, using ground mapping radar, before the ingress on target.

Good job. :)

Portuguese keyboard. It seems I solved the behavior after a clean DCS Beta version install. I was having problems after updating a September version.

I'm also having problems with Communications menu "". It doesn't pop up the menu in all installed modules, even FC3... Tried cleanup and repair DCS, changing \ in all keybindings to another key, it didn't solve. All communications related keybindings are not working, Easy comms on or off, it's the same.

I never used this capability, normally i display CombatFlite on another screen. Accordingly with the tutorial, the CombatFlite generated *.png files will be at 'Documents\CombatFlite\Kneeboard'. Cut and paste on 'Saved Games\DCS\Kneeboard'. https://www.combatflite.com/blog/viggenkneeboard

The AJ-37 was designed for an attack/interdiction mission, when GPS/GNSS systems were only on paper and radio navigation was inaccurate for this mission requisites. :)

Yep, use road junctions for visual fixes at daytime or individual bridges or recognizable lakeshores/coastlines that will appear on radar, at nighttime/low visibility conditions. Map keys or axis for radar gain for contrast enhancement and change radar amplifications modes (page 113), logarithmic for terrain/land cover types and linear for naval use. Be careful with radar on navigation fixes. If radar off the fix will be visual; with radar on the fix will be a radar fix. So, if radar on and want to navigation visual fix, TURN RADAR OFF. When loading data cartridge or entering LS reference (if in another initial airbase than the inputed on mission data cartridge), that information will be entered automatically.

No. BANA Data panel mode is only to input runway headings as if you want to input some road base/FARP with TILS channel and airstrip heading. Use airbase reference numbers for inputing LS/L1/L2 and check output REF LOLA if displayed reference numbers are correct. These are the nuances on using a system designed in the 60s On NAV master mode, align precisely the airplane with the runway and press reference button on stick (map key on flightstick if not yet) for a manual Initial course update to align and correct the heading. Read on Manual page 132 about automatic and manual initial course. For waypoint and LS/L1/L2 input, you have here the CK-37 input codes https://forums.eagle.ru/showthread.php?t=182229 https://forums.eagle.ru/attachment.php?attachmentid=157498&d=1487422933 I strongly advise for some CombatFlite testing on Data Cartdrige exporting. It is very easy to use, just write some coordinates from F10 map if you'll need accurate navigation IP and target positions. As F10 map will display DD MM SS, convert from DD MM SS to DD MM,mm (CombatFlite standard input), using CombatFlite tools. LS and L1 data will automatically added as inserted steerpoint will snap to existing airbases on database; data will be automatically be converted on export. There's the possibility to export maps and mission information as kneeboard pages.

Lots of confusion, here :) My two cents on some thoughts on dead reckoning navigation in the Viggen: After landing, refuel and rearm, before taxiing again, press CK-37 Data panel RENSA to clear mission data. Load data cartridge or input waypoints as required, entering LS reference if in another initial airbase than the one loaded on mission data cartridge; the L1 reference will be automatically identical as entered LS reference (we can input a different L1/L2 as needed). See kneeboard pages for airbases reference numbers. We can use CombatFlite for mission design and data cartridge export. https://www.combatflite.com/ Manual page 132 When aligned at runway, with CK-37 on LS (initial waypoint) before take-off, do a manual Initial course update to align and correct the heading. Manual page 160 It can be useful to make a first waypoint for navigation fix (visual or radar fix), just after take-off. Manual page 169 Fly bellow 500m so TERNAV will automatically update. With data selector set on AKT POS, the 5th digit will display TERNAV status (it should be "5"); 6th digit will be calculated position error in kilometers. Setting radar mode on LAND / SEA (LAND / SJÖ) should be changing the signal modulation on the radar altimeter, but accordingly with RC1 manual version it is not implemented. If a long flight will precede target waypoint, have a IP point for navigation fix (visual or radar). Manual, page 146 When on landing approach set the master mode selector to LANDN NAV, turn to LB 4100m circle at 500m alt to catch TILS and follow steering commands. Navigation fixes will be given automatically by TILS. For a mission, we should have starting airbase LS, navigation waypoints B1, B2 etc, target waypoints M1, M2, etc, pop-up points U1, U2, etc, primary landing L1, secondary/divert landing L2. Navigation fixes will update B1, B2, etc. Updating target position M1, M2, etc with radar, will not update B1, B2 navigation waypoints. See also: Chuck's AJS-37 Viggen Guide Part13 - Navigation & ILS Landing https://drive.google.com/file/d/0B-uSpZROuEd3MThvSmxrN0pUMWM/view Tutorials on Youtube Bunyap Start-up Part 2, Taxi, Takeoff Visual/Radar Nav Fix, TERNAV System, Radar Terrain Avoidance xxJohnxx Navigation System Basics Have fun! :) Cheers.

It's in the works. And it is a factor making me not having it. Yet (give me a Viper, please :) ) See here a summary of what's done and to do. https://forums.eagle.ru/showpost.php?p=3285514&postcount=13 Cheers. ...

There's some opensource information on the cloud, and the general point is that things are getting hairy. Let's actively refrain of not posting here anything political and unilateral. Sent from my Nexus 7 using Tapatalk

After a Windows 10 clean install I tested 104th Phoenix - Operation Longbow on SP and MP. At Singleplayer I experienced some lag and stuttering, 30fps maximum with 8xAF no MSAA (forced 2x FXAA on Nvidia control panel), shadows medium, all other maxed up. At Multiplayer, I had no problem connecting, 50fps stable. It seems the transition from windows 7 and a clean install helped with the above issues.

In my case, I just configured the motherboard BIOS. No halt state and no hyperthreading. I made a BIOS profile, only for this. Sent from my Nexus 7 using Tapatalk

Crashed when loading MP mission. I7 975 @3.33(not OC) 24GB DDR3 1600MHz XMP profile Asus Nvidia GTX1070 Strix OC 8GB VRAM MB Asus P6T Deluxe SSD Samsung 840 - - - - Edit: After the first crash, restarted DCS. Tried to load MP mission; for four times entered the MP lobby just to come again to DCS main screen. Atached "Logs_2.rar" Logs.rar Logs_2.rar

Yep, after not overclock the CPU, no crash happened, as I read somewhere about this problem with Nvidia last drivers, on other applications. After the memory leak on 2.5 Beta it's solved, I'll test again.

Also try to bind processor affinity to DCS, test not using hyperthreading.

Yesterday, after read somewhere about problems with this specific *.dll I tested the Nvidia GeForce Experience in-game overlay (FPS counter) and CPU/RAM overclock (I7 975 at 4GHz, DDR3 1600MHz XMP profile). It seems the last two Nvidia's drivers iterations are having problems with overclocked RAM. No crash after testing the Viggen cockpit and a long session with a Combined Arms SP mission.

Can you be more specific about the solution? It can be important for all. Thanks. Sent from my Nexus 7 using Tapatalk

After testing stop the Asus GPU TweakII application (on a Strix 1070 OC), no crash has happened so far.

Hi. DCS is crashing while entering a mission with this crash log text, only on the Viggen, on singleplayer and multiplayer. The same crash log text on 1.5.8 and 2.2.0. Latest Nvidia driver. Tried to clean display driver and reinstall, no joy. C:\Windows\system32\nvwgf2umx.dll # C0000005 ACCESS_VIOLATION at DBFE8780 00:00000000 00000000 00000000 0000:00000000 DBFE8780 1942C210 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+38DEF0 DBFE9188 1942C280 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+38E8F8 DBFE9482 1942C310 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+38EBF2 DBFD0A1C 1942C3B0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+37618C DBFD14C0 1942C430 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+376C30 DBEA13F8 1942C560 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+246B68 DBEA194D 1942C590 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+2470BD DBE61AFF 1942C8C0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+20726F DBE3E076 1942C900 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1E37E6 DBE1B534 1942C940 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1C0CA4 DBDAC677 1942C9C0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+151DE7 DC67C91D 1942CA40 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+290EBD DC641681 1942F510 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+255C21 DBDA58C5 1942F560 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+14B035 DBC68B2F 1942F650 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+E29F DBE1EFF4 1942F710 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1C4764 DBE3F60F 1942F750 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1E4D7F DBE3F54F 1942F780 0000:00000000 C:\Windows\system32\nvwgf2umx.dll OpenAdapter12()+1E4CBF DC895B5C 1942F7B0 0000:00000000 C:\Windows\system32\nvwgf2umx.dll NVAPI_Thunk()+4AA0FC 779259CD 1942F7E0 0000:00000000 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 77B8383D 1942F830 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+1DCheers. logs.zip

On 1.5 Caucasus map, the information displayed on radar seems coeherent. Did you changed radar elevation? Changing radar elevation angle changes detection angle and information displayed...

I was with the same flickering. I changed the System setting "Water" from Low to High and it solve it.

^ Yeah, someone give us good news :)

For the whiners, complaining that the world don't make turns around them: get a life.