Jump to content

Air to Air Radar


Paco

Recommended Posts

Is it just me or does the air to air radar have trouble finding targets. With the addition of D/L I'm scanning right where targets should be but the radar can't pick them up. Elevation is correction and I've tried different bar scans etc. Nothing. Seems the radar picks them up way inside of where it should. Any ideas?

Paco

Link to comment
Share on other sites

I have the same problem. Also issues with locking targets.

Intel i7 9700K, ASUS ROG STRIX Z390-E, Zotac GTX 2080 TI AMP, Corsair Vengeance 32GB DDR4 3200mhz, Corsair H60 liquid cooler, EVGA 850W PS, Cooler Master: Master Case H500, 1 TB Samsung EVO SSD | Virpil CM2 Throttle, F-16: Thrustmaster F-16/A-10 Stick, F-18: Thrustmaster F-18 Stick | Thrustmaster TPR Pedals | G2 Reverb, J-PEIN Desk mount Throttle, VIRPIL VP-L mount Stick, Cougar MFDs, Generic Custom Built Front Panel, Left Panel and Right Panel, 32 Button Steam Deck.

Link to comment
Share on other sites

So what is this supposed to be? An actual bug report or a rant that the Hornet radar is too bad according to your 'feelings'? Can you be more specific?

''Greed is a bottomless pit which exhausts the person in an endless effort to satisfy the need without ever reaching satisfaction.''

Erich Fromm

Link to comment
Share on other sites

Figured it out. I find the radar works much better with LTWS deselected.

 

 

I just had the same problem. I'll try this next time. Thanks!

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Link to comment
Share on other sites

Figured it out. I find the radar works much better with LTWS deselected.

 

I think you will find that working with LTWS and the different acquisition modes, using L&S designation, AAQC vs. faste acq., return to search and the like will create better habits and SA for when more advanced features are added. There's really no reason to turn ltws off except perhaps to declutter.

 

This post describes a good process under the current implementation (there's been some additions since this was posted, but they have not fundamentally changed the process): https://forums.eagle.ru/showthread.php?p=3961122#post3961122


Edited by sk000tch

just a dude who probably doesn't know what he's talking about

Link to comment
Share on other sites

What question?

 

The discussion of acquisition modes by no.401 Speed is as plain English as it can be made. It’s useful to be precise with terms, as that is the terminology the documentation uses. Recent updates to the manual are quite good.

 

So, plain English - You can command the radar to attempt Single Target Track (STT) by three methods:

 

1 – With LTWS disabled, TDC depress with cursor over brick

2 – With LTWS enabled, Sensor Control Switch right (if radar is on right DDI) with raw contact or trackfile (MSI included) under the cursor

3 - Enabling Automatic Acquisition (AACQ), which will command the radar will attempt STT on L&S if one exists, or, if no L&S then highest priority MSI trackfile

 

You will not get MSI trackfiles but you can disable LTWS and the radar should behave identically as before (#1 above).

 

You can still go direct to STT by #2 above, or, better yet, use #3 by depressing TDC with cursor over brick or MSI track to create launch and steer trackfile (L&S). You then have information to assess IFF status, relative altitudes, range, closure rate, aspect, and decide whether to intercept and whether you should climb/turn/accel without locking target. It’s a good idea to adjust radar azimuth/bars/PRF, though not necessary it will decrease aging and its good prep for TWS. On positive NCTR step station/size/cross section if desired. When you are ready, with TDC assigned to radar, you can “hard lock” by just pressing Sensor Control Switch in direction of radar display to enter STT via AACQ. If you adjusted radar to decrease aging it should be instantaneousA. Then just center dot and pull trigger…


Edited by sk000tch

just a dude who probably doesn't know what he's talking about

Link to comment
Share on other sites

Do you mean when you press designate, and the antennae goes all woogity for a few seconds trying to lock, then gives up?

 

Then you get the blank radar screen and your cursor has helpfully popped to the top left of the display. Then you explode.

 

Cuz I hate that too.

 

 

 

Granted, this can be reduced by leading the brick (don't click on the brick, but click on where it -would- be if it had been moving smoothly on the display), but shouldn't the radar understand that I'm trying to lock the contact, and not the empty space where it was?

 

Genuine question, because sometimes I just guess where the target is, mash designate on empty space, hoping for a lock, and sometimes it works.


Edited by Preendog
Link to comment
Share on other sites

Preendog-

 

There's three designation modes, auto, fast, and bump. There is no "designate button."

 

I assume by designate button you're talking about TDC depress. TDC will command STT if the cursor is over L&S target, but it's specifically advised against. You should not have to guess or lead, if you find yourself doing so take a moment and consider what you are trying to do. TDC depress can perform several functions depending on radar state (LTWS enabled/disabled) and whether the cursor is over a trackfile. In addition to playing havoc with your designation/acquisition, it can command spotlight mode, manually adjust scan centering, etc. The biggest problem is related to closely spaced contacts. TDC depress over the current L&S target will enter STT, but TDC depress over another trackfile will designate it as L&S. Bricks can be close together, aged, and the mechanical action of TDC depress can inadvertently cause the cursor to move - all problematic.

 

If you find yourself "mashing designate," instead of fighting the system in manual acquisition, try using SCS right (w/ TDC assigned to radar on right DDI) to enter AACQ. It's obviously a work in progress, bump acq not in yet, and any given release may break something; but generally speaking using TDC depress over L&S to enter STT is a habit you'll want to break.

 

to each their own though...

just a dude who probably doesn't know what he's talking about

Link to comment
Share on other sites

Figured it out. I find the radar works much better with LTWS deselected.

 

 

 

That did seem to do the trick. I knew where the bandits were. With LTWS on, no bricks (contacts) would illuminate. Once I turn off LTWS they show up.

 

 

Sent from my iPhone using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Link to comment
Share on other sites

Anyone who thinks turning off LTWS will "fix" their radar, is mostly likely just not understanding how to use LTWS (and MSI). I've encountered zero issues with LTWS enabled and I almost exclusively fly a2a in MP and SP.

 

 

 

Sorry, but when LTWS is on....zero returns show. LTWS turned off, they appear. I’ve also done a repair to remove any mods that may have been causing an issue. Same result. This is from an air start in the mission and I don’t even touch the MFDs, same result. Caucuses map as well. So if I am at fault, then why does nothing work when I just let it start from the air?

 

 

Sent from my iPhone using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Link to comment
Share on other sites

Sorry, but when LTWS is on....zero returns show. LTWS turned off, they appear. I’ve also done a repair to remove any mods that may have been causing an issue. Same result. This is from an air start in the mission and I don’t even touch the MFDs, same result. Caucuses map as well. So if I am at fault, then why does nothing work when I just let it start from the air?

 

 

Sent from my iPhone using Tapatalk Pro

 

Ok that's a separate issue

 

For purposes of zeroing out potential variables/errors and avoid getting into search settings, without touching anything else, start with LTWS off and when you acquire raw hits, give it a few sweeps and turn LTWS on. Do they disappear? vice versa?

 

If the mission has awacs or other d/l donors, with MSI and LTWS enabled, do you see hafu symbols on the radar or AOT in the dugout? What about SA Page?

 

Lastly, if you press SCS right, verify TDC is assigned to radar then press SCS right again when you would expect to be within STT range. Does anything happen?

 

If you do the above and have bricks disappearing when you enable LTWS you should probably save a track and submit as a bug

just a dude who probably doesn't know what he's talking about

Link to comment
Share on other sites

A/A Mode & Sensor Configuration

 

Hi gents,

 

Been following your discussion with interest and just wanted to chime in to say that Sk000tch is providing you with some very sound advice. Based on my limited knowledge, I'd recommend that you do not get into the habit of turning your LTWS off as it limits what you can accomplish with your sensor package. More on that below if you're willing to read it all. And that brings me to my second bit of advice. This subject is rather complicated and the functions and interactions of radar and weapons systems takes some effort to understand. Do yourself a favor and study the material because even though it makes little sense the first time you read it, in time you will develop a deeper understanding of it.

 

To add to Sk000tch's comments I've included some material below that I posted today on the No.401 Sqn forum. If you really want to learn more, then read it all, if not, then just ignore the remainder of this post. Sorry it's long, but I can't find any shortcuts.

 

401 Squadron Forum

 

I've been hitting the "books" again after the most recent update to find out what has changed with target acquisition. It certainly seemed like something was broken, but the bug reports and various posts on the ED Forum point to a different scenario. Seems that we (I) have been learning radar target acquisition and sensor/datalink functions and integration within the context of a "work in progress" and what was becoming routine is now evolving beyond an incomplete model to something closer in function to the actual system. Prior to LTWS implementation and perhaps during further development of PLID, UCTR, Datalink etc, it was a simple matter to place the cursor on the target brick and manually acquire and then designate each via manual or AACQ. But now, with these other functions beginning to roll out of the DCS development factory, this "simplified" mode of target acquisition simply does not function as it did.

 

First, many have reported a failure to lock when placing the TDC cursor over a HAFU and trying to acquire/designate that as the L&S. It's happened to me many times and looks like the MC is directing the radar to scan a tight azimuth over the HAFU but then releases it and defaults the radar back to RWS with the cursor high and to the left. REASON: the HAFU symbol on your Attk Rdr display is likely a trackfile being provided to you by AWACS or another donor aircraft via Datalink but that your radar has not yet detected. Possible solution is to place your radar in SIL mode, enter SENSORS on your SA display and switch off SURV function (PB 15). This will clear the deck so to speak, so that you can then switch SIL off, and allow your radar to sweep and detect the targets.

 

Second, AACQ not acquiring new target. If you have designated your L&S via AACQ and want to back out to BVR mode in order to see and select another target on your Attk Rdr display, you must activate the undesignate switch. You also have the option of moving the SCS toward the Attk Rdr display while in AACQ to activate bump acquisition which will place a temporary exclusion zone around the original L&S while it performs a search for another target for ten seconds (note: this will be implemented in future updates). That's along time in a closing fight with missiles inbound, and by then your second target may have closed sufficiently to be outside of the gimble limits of your sweep. So after ten seconds the only target remaining may be the original L&S target (I've had this happen many times where the radar simply returns to the original L&S without every finding the second target). Remember to undesignate when you want to exit AACQ back to full BVR mode. Then you will see your original targets displayed on the Attk Rdr display.

 

Third. Since the latest update, manual acquisition of the L&S target via one depress of the TDC completes designation (as in fast acquisition) preventing you from acquiring a DT2 trackfile. I just learned after reading the radar material again, that since implementation of LTWS, that if you disable LTWS, the radar will lock a target with one depress of the TDC. In order to acquire a L&S target trackfile along with a DT2 trackfile, LTWS must be activated. With this configuration, you can then acquire your L&S target by placing the cursor back over the HAFU with star (L&S) and depressing the TDC a second time, or place the TDC cursor over the L&S and move the SCS toward the Attk Rdr display to activate AACQ. Hopefully, future DCS updates will enable Bump Acquisition via movement of the SCS toward the Attk Rdr display while in AACQ to seek and lock the next target in priority sequence. (Sorry gents, I had to edit this bit as I made an error in how to perform bump acquisition)

 

Read on if you want to get if from the original source:

 

5.3.1 Designation via TDC

Trackfiles can be designated by slewing the cursor over the undesignated HAFU symbol and depressing the TDC. This mechanization only applies to visible HAFU symbols (e.g. TWS, RAID, A/EL format, or RWS with LTWS selected). Attempting to designate a raw hit from VS or RWS (without LTWS selected) will instead immediately acquire it into STT. (that little bit of knowledge didn't stick the first dozen times, so maybe this time?)

 

When the cursor is slewed over an undesignated trackfile's HAFU, a TDC depression designates the trackfile as either the L&S or DT2. If no L&S has yet been established, then this first depression designates the target as the L&S. If a L&S trackfile designation already exists on another trackfile, then the depression designates the target as the DT2. Any previous DT2 designation on another trackfile is cleared. If a designation occurs on the L&S, the L&S is then acquired into STT.

 

When the TDC is depressed with the DT2 under the cursor, the DT2 is upgraded to the L&S designation and the previous L&S is demoted/re-designated as the DT2. This applies to both the Attack format and the AZ/EL format. Note that a TDC depression/release while over the L&S commands the Radar into STT acquisition on the trackfile as described in the preceding paragraph.

 

To summarize:

 

Designating a pre-existing L&S target, enters acquisition (STT) immediately

Designating a raw hit (no HAFU displayed), enters acquisition (STT) immediately

Designating an undesignated trackfile makes it the L&S. If another track was previously the L&S, the old track is made the DT2

 

5.3.2 Designation via Undesignate

Yes, it's a genuine oxymoron. Undesignate can be used for several designation functions, the behavior of which is dependent on whether or not a L&S or DT2 already exists (this has not been tested but I do know that the stepping function has not yet been implemented for the DCS F/A-18C:

 

Initial L&S Designation - When no L&S designation exists, the initial Undesignate activation makes the highest ranking trackfile the L&S.

Target Stepping - When the L&S exists, but not a DT2, the Undesignate switch allows stepping the L&S designation to other MSI trackfiles. With rapid selections of Undesignate, the desired trackfile can quickly be declared the L&S. In this rapid sequence, the MC steps the L&S in the order of rank, through the top eight trackfiles. (NOTE: virtually identical to the bump acquisition function)

 

Target Swapping - When a L&S and DT2 trackfile both exist, the Undesignate switch swaps the designations between the two (assuming none of the overriding conditions below hold true).

 

Other Radar functions that make use of Undesignate take precedence over the Designation functions as follows:

 

Exiting Auto Acquisition (AACQ)

Exiting Spotlight mode

Exiting FLOOD mode

Exiting ACM modes

In any of these cases, Undesignate first performs the aforementioned function and only then can it be used for designation functions.

 

5.3.3 Designation via Acquisition

If the Radar is commanded into STT by any means, the corresponding trackfile is always declared as the L&S if it was not already. For example a TDC designation from VS or RWS (without LTWS enabled), will immediately both declare the trackfile as the L&S and enter STT. Likewise, Fast Acq, AACQ, or ACM modes which all ultimately command STT, will accomplish the same thing. This guarantees that the L&S designation is applied to the desired trackfile even if the acquisition is not successful.

 

FOLLOW UP

 

I ran another few tests with LTWS enabled and was able to acquire separate L&S target and DT2 using manual acquisition. But then after designating the L&S target and upon engaging with a couple of AMRAAM, I could find no quick reliable way to switch onto DT2. The only way that seems to work (sometimes) is to undesignate, wait a second or two for the radar to sweep, then move the cursor onto the second target and depress the TDC twice. It only worked once, when I took a few extra seconds before going defensive (total of 40 sec with a missile literally hundreds of feet away) and managed to get a lock. Every other time as I was evading missiles from the L&S target, I was unable to get a lock on the second aircraft. I would put the cursor over the HAFU, double tap the TDC depress and nothing would happen. I only ever got the second aircraft in ACM mode with the AIM 9x.

 

I only experienced one event when the radar entered a narrow azimuth sweep over a HAFU that I had completed Mode 4 interrogation and which clearly showed a full Hostile reading. In this case I had set my radar to 80 nm as usual, but changed the bar setting to 2 with the sweep setting set to 140 degrees. I could not obtain a lock via manual or AACQ.


Edited by No.401_Speed
Link to comment
Share on other sites

Hi gents,

 

:

:

First, many have reported a failure to lock when placing the TDC cursor over a HAFU and trying to acquire/designate that as the L&S. It's happened to me many times and looks like the MC is directing the radar to scan a tight azimuth over the HAFU but then releases it and defaults the radar back to RWS with the cursor high and to the left. REASON: the HAFU symbol on your Attk Rdr display is likely a trackfile being provided to you by AWACS or another donor aircraft via Datalink but that your radar has not yet detected. Possible solution is to place your radar in SIL mode, enter SENSORS on your SA display and switch off SURV function (PB 15). This will clear the deck so to speak, so that you can then switch SIL off, and allow your radar to sweep and detect the targets.

:

:

I only experienced one event when the radar entered a narrow azimuth sweep over a HAFU that I had completed Mode 4 interrogation and which clearly showed a full Hostile reading. In this case I had set my radar to 80 nm as usual, but changed the bar setting to 2 with the sweep setting set to 140 degrees. I could not obtain a lock via manual or AACQ.

 

Good read, thanks. Which is why I posted this (https://forums.eagle.ru/showthread.php?t=247394) to better understand HAFUs since some cannot be locked up. Which then leads me to another question...

 

A donated track/HAFU shows up that your radar has not yet detected. You can't lock it up. You need your radar to pick it up. Distance is known, I presume by estimating from the radar range? Azimuth should be easy. But what radar altitudes do I scan to pick it up? Also, sometimes I can't seem to pick it up at all at longer ranges (40nm+?) esp with the M2000C if I recall right. Is jamming or something modeled such that certain aircraft are just difficult to pick up on the F/A-18's radar?

AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 32GB Adata Spectrix D50 3600 Mhz (16x2) | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4
HOTAS Warthog | TrackIR 5 |
My Files | Windows 10 Home x64

Link to comment
Share on other sites

Periodic Acquisition Failure

 

Hi GrEaSeLiTeNiN,

 

Short answer is "I don't know". I can say that of the ten or so tests that I ran in an identical 1 vs 2 scenario, half with and the other half without AWACS/Donor support, there was one during which I was unable to achieve a lock by any means. It may just come down to a periodic glitch in the sim software?

 

Excellent chart. Something like that should have been in the Hornet manual.

 

Cheers

 

Speed


Edited by No.401_Speed
Link to comment
Share on other sites

Manual Designation versus Automatic Acquisition

 

I ran a few more tests to confirm that the Hornet's radar can still detect out to 75-80 nm with LTWS enabled. No problems. Detection ranges seemed comparable with LTWS on or off.

 

Next I wanted to re-test manual designation versus automatic acquisition using AACQ. The tracks attached demonstrate how update 34108 behaves in either mode. I have no mods and I use the techniques described by Wags in his training videos.

 

The first track shows target detection without any Datalink donors. The HAFU are depicted in yellow with only the top portion displayed, ergo ownship data. I proceed through Mode 4 interrogation and the radar returns fail the IFF and remain yellow, however because only one source (ownship) is providing return data, the HAFU remain yellow. In order for you to achieve Hostile confirmation, you would need to get within +-20 nm, in a relatively high aspect angle and complete a UCTR. That's a bit too close for comfort. I then designate each raw return as L&S and DT2. Once within range, I depress the TDC over the L&S to acquire it into STT. The first target is engaged, then the second target is designated and acquired as the L&S and engaged.

 

The second track shows the same engagement, no AWACS, using AACQ after Mode 4 interrogation. You can see problems with achieving and maintaining a lock and it must be done repeatedly throughout the engagement. Don't know why this is?

 

Note about these tracks: You guys are probably pretty familiar with the different outcomes that a replay can deliver, so if it looks like I'm chasing empty sky or focusing on the ground with nothing to see, you'll understand why.

DCS Open Beta 25534108 Hornet Radar Designate LS_DT2 Successful Bump Pilot Speed 14 Aug 19.trk

DCS Open Beta 25534108 Hornet AACQ Pilot Speed 14 Aug 19.trk

Link to comment
Share on other sites

I ran a few more tests to confirm that the Hornet's radar can still detect out to 75-80 nm with LTWS enabled. No problems. Detection ranges seemed comparable with LTWS on or off.

 

 

 

Next I wanted to re-test manual designation versus automatic acquisition using AACQ. The tracks attached demonstrate how update 34108 behaves in either mode. I have no mods and I use the techniques described by Wags in his training videos.

 

 

 

The first track shows target detection without any Datalink donors. The HAFU are depicted in yellow with only the top portion displayed, ergo ownship data. I proceed through Mode 4 interrogation and the radar returns fail the IFF and remain yellow, however because only one source (ownship) is providing return data, the HAFU remain yellow. In order for you to achieve Hostile confirmation, you would need to get within +-20 nm, in a relatively high aspect angle and complete a UCTR. That's a bit too close for comfort. I then designate each raw return as L&S and DT2. Once within range, I depress the TDC over the L&S to acquire it into STT. The first target is engaged, then the second target is designated and acquired as the L&S and engaged.

 

 

 

The second track shows the same engagement, no AWACS, using AACQ after Mode 4 interrogation. You can see problems with achieving and maintaining a lock and it must be done repeatedly throughout the engagement. Don't know why this is?

 

 

 

Note about these tracks: You guys are probably pretty familiar with the different outcomes that a replay can deliver, so if it looks like I'm chasing empty sky or focusing on the ground with nothing to see, you'll understand why.

 

 

1. You need to STT the contact to get an NCTR ID on it. I could never get NCTR ID otherwise, even when very close and head on.

 

2. Yes, seems to be the case now that you may need repeated locks with AACQ. I recall reading a post by dev that AACQ is still sort of WIP.

 

3. Which enemy planes were used in your tests? Any difference between say M2000' F14 MiG29?

AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 32GB Adata Spectrix D50 3600 Mhz (16x2) | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4
HOTAS Warthog | TrackIR 5 |
My Files | Windows 10 Home x64

Link to comment
Share on other sites

Radar Range & Target Acqusition

 

Yeh the original tests were all done with the MiG-29s. I just ran two more scenarios as a possible answer to Paco's original question. First scenario much like the original except that I spread six aircraft including the Su-25, Su-27, Su-33, MiG-27, MiG-29, Mirage 2000 at a range of 120 nm at altitudes ranging from 30-40,000'. Radar was set at 4B, 160nm, 80 degree sweep centered at approx 10nm. In the pic below, you can clearly see that all six aircraft are detected within that 80 degree sweep. So with no AWACS or donor support the latest update now .34644, the Hornet radar seems to be working fine (aka under ideal conditions).

 

 

I think the second pic might answer Paco's question. I ran the test a second time at a much closer range and purposely set some of the bogeys beyond the 80 degree sweep. I knew they were out there only twenty miles or so in front of me, but the radar cone sweeping to my front just could not detect them. Part of the learning process is how to manipulate and leverage your sensor capabilities. Case in point: at such close range about half of these aircraft got behind me (I cheated and only armed them with guns) but I managed to track them all down except the Su-33. I couldn't find it by sweeping with AACQ enabled, so I switched to ACM and initially used VACQ as I turned a tight bank looking for it. It was not until I used WACQ and uncaged it to scan the horizon as I turned, that the radar finally picked it up low and just below the horizon. So knowing the unique capabilities of each sensor configuration and then matching that to the best weapon for the job, will help you locate and bring down your target.

955444353_HornetRadarVarious75to80nm35000feet.thumb.JPG.e9cd4b52b8c95f40a5f02dd857f1631c.JPG

1351890090_HornetRadarVarious20nm33000feet.thumb.JPG.8e5d70bb1d91633bed0672de15db601b.JPG

Link to comment
Share on other sites

After the 15 Aug update, first thing I noticed in my custom mission is this (see screenshot) - green bricks in HAFUs (in the red AWACS contact and yellow HAFU). The red diamond/green brick is a pair of Mi-24s - but AWACS picked up only one in the pair? (The 2 bricks on its left are a pair of AH-64s.) The yellow HAFU/green brick is a pair of Su25s - but again, the donor aircraft identifies only one in the pair? Hmmm..

 

Also noticed now you can lock up a donor target if your radar altitude & azimuth are set correctly, ie, target is within your scan limits - adjust radar altitude until TDC cursor (which is placed over contact) shows an altitude range that covers the contact's altitude (BRA) as given by AWACS. Otherwise, the vertical scan line will do that 'quick dance' and not be able to lock it up.

 

drmrhnc.jpg


Edited by GrEaSeLiTeNiN

AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 32GB Adata Spectrix D50 3600 Mhz (16x2) | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4
HOTAS Warthog | TrackIR 5 |
My Files | Windows 10 Home x64

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...