Panny

Yeah I do use that quite a lot, but I'd also like to change between vanilla gnd stab and NAVGRID so I can easily get a centered view

Hi there, Just wanted to collect a few things in which it would be great to have some added functionality on NAVGRID. 1. NAVGRID manual reference from map Since the last update, when you input NAVGRID ref from map(i.e. Bullseye), Jester will input what he thinks to be altitude. Since YY is just a reference point however, he just shifts the grid coverage. It's not a big issue, it's just weird to see him do it. I believe he also tries to enter the 'altitude' even if you manually provide him a coordinate. 2. With Jester NAVGRID functionality, is it possible to be able to manually tell Jester our desired grid coverage and threat axis? The existing method of grid heading absolute and grid coverage is moderately useful(grid heading relative I don't fully understand), but would be far better to just input the desired numbers much like how we can manually enter the coordinates of a waypoint or YY. 3. Is it possible to have a Jester specific binding to enable and disable NAVGRID? I use this function quite a lot, but it's quite a few menus to get through(contextual - main - navigation - navgrid). I'm aware that NAVGRID isn't something that's frequently used by the wider community, no less without a proper RIO, but it would be greatly appreciated if some of these changes were made to have a little more fidelity over the function. If you have any further questions, or need me to provide anything more please don't hesitate to get in contact. Cheers, Peter Additionally - it would be great in the Beyond Visual Range/Within Visual Range/Contract Jester menu to have the option to disable his TCS function, or adjust at what ranges he attempts to gain a VID. When you STT a contact, regardless of range, he'll attempt to spot it via the TCS meaning you briefly lose TID information such as target aspect or the velocity vector of the contact. To have him just leave the TCS alone would be excellent while I manage my BVR timeline. Cheers!

Should probably just fly better next time

Posting this from another thread: Hi there, Can we add a Jester function to disable him using the TCS? When you get an STT lock he kind of goes insane with it, and within a BVR timeline I lose things like target aspect/bearing or altitude, or just the vector of the contact that I would really like to see. I think it's a fair trade off, since I would lose the ability for Jester to VID when I have it disabled. Cheers!

So there was a thread somewhere about suggesting Jester, but I can't seem to find it?

Hi there, Can we add a Jester function to disable him using the TCS? When you get an STT lock he kind of goes insane with it, and within a BVR timeline I lose things like target aspect/bearing or altitude, or just the vector of the contact that I would really like to see. I think it's a fair trade off, since I would lose the ability for Jester to VID when I have it disabled. Cheers!

Hi there, Noticed a typo on Set Ripple Quantity: Cheers! Peter

Credit to our member Thomas 'Teabow' Thibaut for making this clip! Want to find out more about DCAF - join our Discord here: https://discord.gg/dcaf

I haven't tested with RIO. Can only say without a human RIO.

I would just like to throw my 2 cents in and say this happens regardless of RIO or not... That said, it's the spawning aircraft that causes the problem more than anything else

I think this occurs regardless of stick. I use Virpil F-14 stick and same problems occur as you describe. As I understand since last update of flight model, autopilot had been borked a bit

I'll have to run it again. With my flying group I did have others test it and found it affected 75% of people, but not all.

I would like to add my two cents on this quickly. We have this issue, and what it seems is that for a split second when a new Tomcat spawns in, its wings are unswept. Once it is spawned, the wings are swept. In that split second, it causes a collision and damage of varying severity. My group and I once tried immortality triggers to prevent it, but what we found is that the trigger doesn't kick in before the spawn, so damage is still caused.

Tell me about it. Drives me insane and really kills half the experience

I don't that was the case, since they were all Co speed

Also - I wrote this post which you may find helpful:

It's not an SC specific problem, happens on all carriers. Seems to be a wing desync issue when clients spawn in. What ED is responsible for is the catapults. If an F-14 takes CAT 1, cat 2 locks out until launch. If cat 2 is taken, all other cats are locked out. Weird behaviour

Hi there, I've just started getting this issue and it's driving me insane. It seems that with how the Mission Editor compiles certain missions, it can cause the lead F-14 of a mission editor to crash the client's DCS. It can be immediate, it can crash after a few minutes. I though it was a problem on my side, but I've wiped and reinstalled my DCS and the problem is still there. Interestingly, the bug can be avoided by recompiling the mission in Combat Flite. Anyway, it's extremely annoying. Bug: Certain missions cause the lead client F-14 in an ME group to crash their DCS. Can I reproduce it 100%: Yes. How to reproduce/ description: I've uploaded a mission, which is an edited version of Heatblurring the Lines. Try either unit 1 of the first or second F-14 group. Notice the problem does not occur with any of the other Tomcats. DCS Version: DCS 2.7.8.16140 Open Beta System Specs: 5900x, 3090, 32GB RAM, 970 Evo, Win10 64Bit Mods: Some liveries, that's it. This is a very frustrating issue, and I'm hoping I'm not alone on this, since I really don't know why I'm getting it. Cheers, Peter (4 ship CAP) Operation Odyssey.miz

Visual explanation:

Hi there, Is it possible that when hooked to the catapult the user could still have access to the navigation steerpoint wheel? Currently it seems that if you bring it up you can only change TACAN. I know it's a niche thing, but due to the Tomcat spawn problems on the carrier(the wing desync), our squadron has decided just to spawn on the catapults. Often we have to add more waypoints/info, which would be vastly more preferable than doing it in the air(especially as flight lead). This is a very small and minor thing, but would be very useful. Cheers, Peter

Apologies on pushing this, but any thoughts?

Hi there, I've been slowly trying to familiarise myself with the ME. One of the things I want to try and solve are the multiplayer spawning problems the F-14 has(in short client F-14s that spawn next to each other briefly collide due to desync with the wing sweep, leading to them being damaged to varying levels). It seems that this F-14 bug isn't being addressed, so I'd like to create a workaround. In my scenario, I've set a trigger zone over the path of the carrer, for the first fifteen or twenty minutes of its cruise since mission start. For the F-14 group, I have set in advanced waypoint actions - perform command - immortal - set flag (3). Additionally, as pictured below, I have the following triggers set. Interestingly upon spawn, the F-14s will become immortal, recognising that they are in the zone. When I fly out of the zone, I can tell I have left it, since I bound a message to inform me if I have left. However, for whatever reason, I do not become mortal again. I'm somewhat confused as to why the second trigger is not activating, since in effect I'm working the inverse of what was required to activate it. Is it possible that advanced waypoint actions can only be activated once/aren't toggled? I have attached the pictures above in the hope that you may spot something I missed. Kr, Peter

Do multiplayer people still get collision spawn issues with the Forrestal?