Leviathan667

Thanks master QuiGon

Follow up question: is it possible to put a TILS beacon next to a road?

Has anyone tried to land on roads at night? I find it impossible after a few attempts. I use smokes with fire to mark the location of the road but it nos enough. There really is a need for full lighting along the portion of the road used for landing. Can I add the necessary lighting in the mission editor?

GR. 1A with the ability to carry ALARM anti-radiation missiles & the B version with the capability to carry the Sea Eagle anti-ship missile

I forgot to mention the issues I reported were found on the OB version. I also posted videos to yourube show how the module behaves when those SPA features fail

Removed the A-4 mod and it works now. Thanks

Edit: landed on aircraft carrier so the problem is only related to land.

When landing on land runways (tried Senaki in Georgia and Liwa in the UAE), the plane will go through the runway and sink into some subterranean sea, under the air base. See screenshot. (note: the VSI/HSI are off because I ran out of fuel a second before I was supposed to touch down on the runway and it has nothing to do with the bug I'm experiencing as I did land without running out of fuel before with the same outcome) I updated from 2.5.4.something to 2.5.5. 32299 (14th June) so I skipped the first 2.5.5something update.

There's a glitch in the video rendering in HB Tomcat Iran Reactor Strike.miz as background dust smoke seems to affect the rendering of the frame of the cockpit. See screenshots for illustration. Hope this helps.

When Jester dhas been "incapacitated" or after he had ejected, if I press A the wheel will show up. When I press A again to make it go, it will not.

I get it. Thank you for your helpful answers. HB, please do not consider this post a bug report.

EDIT: HB, please do not consider this post a bug report. It seems this happened because I broke the gyros after a 10G turn. Not sure if it is a bug or something that can be fixed while in the plane but after a prolonged dogfighting session, the lines on the HUD and VDI stopped being parallel to the plane's flying plane.

Hi, By default DCS will store screenshots and miz files to the following folder C:\Users\username\Saved Games\DCS.openbeta I'd like to change this to D:\DCS\ How can I do that? Thanks

thanks Stuka

Same issue here. I run DCS in 2k on a 32in screen (+TIR 5) with most graphic settings maxed out. On the F-14 gun training mission, I can hardly spot enemy planes farther away than 1 or 2 miles. And even then, they appear as a tiny collection of formless dots and you cannot identify them for what they are (in this case, I went straight to WP3 and Mig-23s as I entirely missed the F-5s). I don't have that issue with the F-18. I recently watched when it comes to spotting enemy planes from afar. But the F-14 issue seems to be different: it's about spotting planes from far away as well as up close. Do note also that I usually don't use labels. I've been practicing dogfighting without labels in the F-18 for a few months now.

thanks. Just discovered CombatFlite! Grea tool

Thanks for your good comments :) I hope HB will fix the issues we uncovered with the SPA mode.

Looks like you’re a developer so I tried documenting the issues people meet when using SPA mode. I may also be doing things the wrong way, Either way, it can only help to clarify what’s going on here. According to the AJS 37 Manual RC2 (2019-01-16): #1: “M1-M9: Reconnaissance targets. (Indicated by a red M on destination indicator). Note that the reconnaisance target points (Red M) are not normal target waypoints (White M, converted from B points) but entirely seperate (White M, converted from B points).” (p. 360) What actually happens: Neither M# nor red M#9 ever appears on the destination indicator (where # stands for any digit between 1 and 9). The destination indicator remains as it is, i.. showing the B# waypoint. This fact is being shown the videos below. #2: “Other displays are slightly changed in the following manner: (2a)“Timekeeping is paused, airspeed deviation fin is reset. What actually happens: It seems to be working regrding the timekeeping feature. TID shows a frozen time to waypoint (e.g. 700055 15 km from won the way towards B1). I did not test the airspeed deviation feature. See video: (2b) “Fuel requirement is between the current position to the primary landing base, based on to requirement need to return to base with current parameters along with the set fuel reserve.” What actually happens: Does not seem to work. When I cycle from NAV to SPA master mode, the striped fuel needle does not change position (eventhought I did it just a few minutes after take-off). I had also set the fuel reserve warning at 20% beforehand. See video: (2c) “Automatic destination change is inhibited. When changing from mode SPA, the previous destination waypoint will be selected automatically.” (p. 361) What actually happens: The first sentence is verified: It’sworking! Not sure how to interpret the second sentence though. #3: “The patrol area is only displayed if the master mode selector is in mode SPA and the radar mode selector in modes A0 and A1. The RUTA display is automatically selected on switching to master mode SPA.” What actually happens: It works! #4 “Discovered targets can be measured visually or by radar, similarly to a normal target waypoint. In mode SPA/MÅL, a target fix is not made for an existing waypoint, but a new reconnaissance target waypoint is created for each defined reconnaissance target instead. The longitude and latitude of the contact as well as a timestamp of the target fix is stored in the system. The system can store up to 9 reconnaissance position targets M1-M9. Each new reconaisance target will be stored in sequence M1-M9. Any new target will be assigned to the next number in the sequence.” (p. 363) “Radar fixes are made by setting the radar mode selector to A1 and making a radar fix on the ship’s radar contact (similarly to how a normal radar fix is made by maneuvering the cross onto the target and pressing TV). “The data panel will indicate the bearing and distance to position of the radar cursor (cross). When the fix is made, the data panel will alternate between longitude and latitude on the first five digits. The sixth digit will alternate between a minus sign (when displaying longitude) and the reconnaissance target number (when displaying latitude). The CI will display the completed fix point with the circle marker until a new destination is set, or a new fix is prepared. ” (p.364) What happens: At first, the radar fix seems to work. It will show what seeming are the target’s coordinates and that they have been saved as an M# point although it is white and not red. But the recorded coordinates are inconsistent: for example, when I did the first (M1) radar fix in SPA mode, it showed the following coordinates: LO 40064_ LA431621 After a few minutes, after I had switched back to NAV mode: switching again to SPA mode, selecting M1 in AKT POS, then swithing to REF LOLA on the datapanel selector, the M1 coordinates that show up on the datya display are not the same: LO410544 LA424828 This is a place south of Sukhumi. The ships I did the fix on are next to Sochi. It tried two more times and recorded the entire process with the M3 radar fix in SPA. Video: -when I did the radar fix in SPA mode, it showed the following coordinates (they seem to be accurate since I put ships in their general vicinity - close to Gelendzhik) : LO37581_ LA442953 - After switching back to NAV, then SPA again, then selecting M3 in AKT POS then switching to REF LOLA: LO364716 LA435945 This location is in the Black Sea, a little more than 100 km west of the actual radar fix that has been made earlier. I did another video showing the whole process from the initial coordinates that show up on the data display and those that show up after swithing back to NAV then again to SPA: Moreover, even if a radar fix in SPA mode has been done and recorded in an M# waypoint, switching back to NAV will change the Destination indicator to a blinking E# as if the system is stll expecting a fix. This can be corrected by releasing the fix trigger (T0). #5: “Transfer to tracking target Data from the target measurement mode (MÅL) can be transferred to the target tracking mode layer (SKU). This is done by selecting the desired measured target in SPA/MÅL and then pressing the waypoint button LS/SKU twice in rapid succession. “A successful transfer is indicated by the tracked target number (S1 – S9) in the destination indicator.” “A failed transfer (due to the tracking slots being full) is indicated by six minus signs.” “Transferred targets are assigned the lowest available tracking slot number.” (p. 365) What happens: It doesn’t seem to work. No S# waypoint appears on the destination indicator (the normally red - but this does not work here) M# waypoint remains unchanged). And no failed transfer message appears either. See video: #6: “Mode SPA/SKU is selected, in mode SPA/MÅL and with the data selector in AKT POS, by pressing the waypoint button LS/SKU once. “This will result in the either latest selected, measured, or transferred target in the SKU layer being selected as a destination.” (p. 366) What happens: “When switching from NAV to SPA, then pressing LS/SKU, nothing happens on the destination indicator (it keeps showing the waypoint towards which the plane is heading (e.g. B2)). #7: “In mode SPA/SKU, only targets in the SKU-layer can be selected as a destination. A target is selected in the SKU layer by choosing the data selector mode AKT POS, then pressing the number (S1 – S9). As the tracking targets cannot be selected in any other mode than SPA/SKU, the mode is indicated by a tracking target being the destination (S on the destination indicator).” What happens: Nothing. I switched from NAV top SPA then pressed LS/SKU with the data selector mode in AKT POS. Nothing changed on the destination indicator (I was flying towards waypoint 2). #8: Fixes in SPA/SKU (p.366-8). Cannot test since no S waypoint shows up on the destination indicator. #9: Several other functions (p. 369-70) (a) “Several reconnaissance functions are only programmable / accessible in mode SPA. Normally, pressing the RENSA (CLEAR) button while airborne will result in that the fixes being cleared, in mode SPA the button has other functions: In mode SPA / MÅL (recce target measurement), the latest selected / measured target is cleared on the first press of the button, the second will clear all the measured reconnaissance targets if pressed within 2 seconds of the first press and no digit button or fix trigger has been pressed in-between.” What happens: Nothing. The following functions have not been tested: Clearing individual targets in SPA MAL, clearing targets in SPA/SKU, Input VIND/RUTA/MAL, Input TID, Input TAKT,Output VIND/RUTA/MAL, Output TID, Output TAKT.

Hi, Not working : The S waypoints when you try to follow a target and the red M waypoints when you do a radar TV fix. Did not try the transfer of the data from SPA MAL to SPA SKU so i can.’t say

You got that nickname from Tintin?

Very good job! Thanks

I am trying to improve my situational awareness these days but the learning curve is not as steep as I'd like it to be I’ve identified several issues . Any of the following statements may be wrong or show that I am missing something important and I would appreciate if you let me know what and how to get better at it: IN A DOGFIGHT: - I’d better keep my eyes glued on the target from the merge onwards. Otherwise, it’ll take (too much) time to visually reacquire it - in ACM mode, the radar will, most of the time, not lock onto a target that passes through the scan area (this one is very frustrating since you cannot trust your eyes will always spot the enemy even when it’s in front of you - depending on what’s in the background). In a turning fight I mosty use it in vertical acquisition mode which should provide for a large horizontal radar coverage (I don’t know how thick the beam is though) - usage of the AIM-9 seeker is of limited value as the sun may disrupt it and it does not cover a wide area anyway plus it is sound based and will not provide strong visual cues - JHMCS is not linked to any IRST device as on the Su-27 (my understanding is that the latter will track any nearby IR signature - though not in a 360° field - and show a cue on the pilot’s helmet mounted display). - use of the AWACS is of limited value since an enemy plane at BRA 101°, 2 nm, 10 500 ft when the AWACS detected it may very well be 155°, 1 nm, 9 000 ft after you get the message and start looking for it WHEN IN BVR: - provided at least one plane on either side has survived the volley of medium range missiles and that I am one them, and in the absence of a merge, I find myself always at a disadvantage (and more so against the AI than human players) because it is so difficult to visually spot an enemy plane more than 3 nm away and the F-18’s radar is too slow/inefficient at locking targets when in ACM mode. When it comes to the hardware I use, it’s the following: 32” 2560×1444 on GTX 1080 with most settings maxed out. I recently got the 32” monitor (I had a 27” 1920×1080 before) and it made a significant difference in my ability to spot enemy planes while dogfighting. But I am under the impression I could be better at it, notwithstanding the material I use. Any tips will help! Thank you

It's been a year it has been reported radio COMM 2 is not functionnal. It seems to me it is still not working but then I am new to the Harrier and maybe I am doing sthing wrong?

While I was about to vote on the poll, I stopped a few secs and thought: I'd love an a map of Afghanistan but ... the country is a desert with mountains, just like Nevada. Cannot make my mind on which part I'd like to see modeled.

I concur with the above. Thanks for laying down the resona why Heatblur should or would make a Tornado mod