All Activity

Ahhh see I was thinking during the cold war. Like a late 1970s or early 1980s update just to get pulse doppler retrofitted. Even if the set couldn't do TWS, had a shorter range, or smaller scan volume, pulse doppler seems like it would be so much more capable particularly in the low level ground attack role the F-4 found itself in. Make it more able to defend itself. By 1991 it doesn't make sense to me to upgrade it unless you just can't afford anything else. But yes I guess money isn't unlimited.

Ahh lemme check... Yhea, I really don't care what you think.

This! This is what should have been the FF module. Not the A as in Ancient...

@Hiob Thanks for the insight. Adding the oil cooler about 50% open seems to help. If you follow the training mission for carrier landing in game, you're instructed to "close the cowl flaps". Gotta give that training instruction an "F". Having the cowl flaps full or partially open seems to be the only way to make through without seizing the engine.

Just change the program in DTC. The manual is out of date regardless now

Где поискать, не подскажешь? Или название, что за мод.

Latest update from the ED folk on the bug report in their Discord was that they were able to replicate, and now appear to have fixed as can no longer replicate in their testing version. Based on this feedback it looks like we might get this fix in the upcoming patch (hopefully this week).

Latest update from the ED folk on the bug report in their Discord was that they were able to replicate, and now appear to have fixed as can no longer replicate in their testing version. Based on this feedback it looks like we might get this fix in the upcoming patch (hopefully this week).

Would be a good addition to add for conflicts in the indo-pacific region, Nothing radical capability-wise here, but it would certainly be a start for aussie assets in the game!

Just a quick note to say how impressed I was with the relative ease of setting up Skyeye on a home machine. It was less than 30 mins work, mostly because I couldn't remember how to change my server's Tacview settings. I'm still shocked that it hasn't been adopted by more mp servers. When it's processing a transmission, I notice the CPU usage spikes up to 100%. Does that mean Skyeye is spreading the load effectively over all cores? Assuming I stick to local processing on a PC, would it benefit from a threadripper or other CPU that's big on core count? Does anyone else have other ideas on optimizing response time other than using the quicker language model? Thanks again for all the work. It's another example of the strong community support that brings life to DCS. Oh, I just remembered my other question. Is Skyeye impaired at all by that radio effects simulation of SRS? Surely decreased sound quality of a simulated radio transmission is making Skyeye work harder to understand what's said.

No, I don't have an iPhone. And comparing DCS to some random smartphone sim tells us nothing of consequence. And you haven't answered my question: what do you consider to be incorrect regarding the arresting wires. Incorrect, that is, in comparison to how the real-world arrestor cables behave, which is the only thing that matters.

In IL2, I've had occasional occurrences of the unit going black screen. At first I thought I was accidentally fingering the power button but it wasn't that. It's happened both in-game and while on the PP home screen.

Any updates?

ED fixes weapons, not the 3rd party devs. It is frustrating when they say 'Reported', lock the thread, and then ignore it for months and months though.

Several users who held onto their F-4’s into the 90’s and early 2000’s did modernise the radar with a new set, however by then in US service the Phantom was on the way out. I guess it would be cool to have one of those variants, though to be honest we would end up destroying some of the charm of the current module with how challenging the radar is compared to more modern jets.

Before complaining, I'd like to say that I really enjoy these missions... Mission 3, after completing the first engagements and refueling, as I am travelling towards the second engagement, I receive this strange "advisory" that I failed the second engagement and then the mission automatically ends after the 5 sec countdown... What happened ?

Long story short, I like to create "free flight" missions with populated air bases and airports to at least give me the illusion of the world being alive - but I'm having some difficulties finding out what was based where in East Germany. West Germany seems to be well documented, but for the East I'm finding a lot of conflicting accounts on what was based where. If anyone know of a reputable source for what aircraft were based at what air base in Eastern Germany I'd be very happy if you could share it.

Haha! Makes sense! [emoji1] Take care! [emoji1303] Sent from my SM-A536B using Tapatalk

I had no issues until I was sent to intercept the enemy. The callouts from the Awcs said the altitude was 15.000, but in reality he was at 1.000 feet. The bullseye references was correct though. He was extremely fast and I ran out of gass before I could hit the tanker after being called off the chase... Apart from this issue with the altitude callouts the mission seems to be fine.

Happy to help! [emoji1303] Sent from my SM-A536B using Tapatalk

We already have a way to source that data for the GPS. after i get the catalog and waypoint entering working, im gonna move onto automatically adding all the airfields, beacons, etc. into the database at runtime.

ok, NTTR is relative easy cause that the US had good data sources for aeronautical data. If you need the beacon data from DCS I have a script for a quick read out.

Not sure what your use case was but DCS has native support for this now so instructions re: Nvidia Profile Inspector, Nvidia app, etc. are no longer needed if you're just wanting to use in DCS.

yup. our target map really is NTTR. Its got all the accurate VOR stations, I think most of the ILS beacons, runways line up perfectly, etc.