All Activity

Just tested, works on my end. Could you supply a track please?

Wow, I mean WOW, 11 years!! There was a time a while ago when it was 7 years, then people started saying 8 years (neither of them true, make it 3-4), but apparently the time it took grows and grows every time someone uses that for an argument and now it's peaked at nothing less than 11 years!! WOWWW , it's the miracle of the M3 Corsair's ever growing development time . Next time I hear about it I'd expect it took not less than 15 years

Yes, this feature is called "focus" in Jester for the F4. You can use the context command (V) or the Jester Wheel for it. Details in the manual: https://f4.manuals.heatblur.se/jester/combat/radar.html#target-selection

https://www.digitalcombatsimulator.com/en/files/3313266/

I figured it out finally. I was practicing at the outer sides of the caucasus and pavespike does not work there somehow. I posted below.

Hey there. I got some ready to ship early next week. Standard Edition. Best shoot me a DM on discord srf_winger_73_david

What firmware on your Super? And what Pimax Play version?

Thanks!

I assume Discord. Sent from my SM-A536B using Tapatalk

can you please share the download link? I can't find it anywhere

Are you in the correct mode? Type 1, Jams on nails Type 2, Constantly jams I've experienced no issues with it.

The map is in deed not very FPS friendly as you said. First rule is to avoid opening the F10 map in your server session because this eats up your VRAM quickly. In the Phantom I sometimes have a hard time getting a smooth session. In the F16 it is a little better, cause the module is not that FPS hungry as the Phantom or Strike Eagle. My biggest Problem with the F16 on this map, is that it is historically inadequat. Since you cannot use Fox 1 with your Viper you are forced to use Fox 3 which doesn´t fit into a late 80s cold war setting and is quite overpowerd. But that was not the question. Maybe you have to lower your settings to gain some fps. But with a 3090 and the usual tweeking prozess this should be manageable.

Thanks. This made it playable for me, The magic growing and shrinking mushroom / bush / rock effect was ruining it.

Temporary fix here. This makes a world of difference at low level where the "magic mushroom" bubble cant be unseen once you notice it. Doesn't affect grass and trees.

Would be nice to see this eventually be added to the ED modules. And it's been request many times. We know it shouldn't be that hard as a previous dev team was able to add it within a patch window.

Naughty boy

In cockpit view, try hovering the cursor over the door area and look for a small hand or highlight — some aircraft use context-sensitive hotspots that only appear at certain camera angles.

@obious Are you talking about the simulation or the animations? Sent from my SM-A536B using Tapatalk

Did you consider including the still classified "temporal anomaly" incident that - allegedly - happened to the USS Nimitz in 1980? Where Tomcats from VF-84 - allegedly - splashed two RJN Mitsubishi Zeros (that looked suspiciously like re-painted T-6 Texans)? Would be a nice Easter egg, especially the narration could potentially be hilarious.

You can see it on this stream (timecode 12m44sec) https://www.twitch.tv/videos/2563969490?t=00h12m44s

I'm sure if ED decided to make an M2000-5, it would be a top. The entire French community would jump on this module. Me first. But I think it's not ED's desire to do it, but the lack of freely available documents and Dassault's authorization. It will remain a dream...

Hi, we will need track replays from both sides to try and reproduce this. If possible use caucasus terrain and just the units needed for the test. thank you

I would be cool if we had something of an option to use custom files to replace the default "Rita" VIWAS. Apparently it was something local units would do. Maybe I'll get my wife to record the aural warnings in her sexiest Russian accent

Thank you all for input folks. Very helpful. I've decided to go with a 5070ti + Core Ultra 5 245KF + 64GB DDR5 6000. Hopefully it will get me what I want.

Hi all, I’ve got a question about handling radar contacts in the F-4E with AI Jester. Let’s say I already see a (IFF) contact on the radar. At this point I don’t want to hard lock it yet — I just want Jester to keep following that contact area so he doesn’t lose it when he resumes his wider search pattern. Sometimes it feels like if I don’t lock immediately, Jester just keeps scanning, contact is lost and it can take too long before he reacquires the same blip. So my question is: Is there a way to tell Jester to “track” or “focus” on a contact without going to a hard lock? Do you guys use specific Jester Wheel entries or context button tricks to make him hold a radar focus on a contact? Any tips or workflow that help reduce the chance of losing a contact before I’m ready to commit to a lock? Curious to hear how others handle this — thanks in advance! Cheers, Zev