Wizard1393

Also, am getting mixed results with Jester and A2A engagements. Seems like I have to be pretty much on the exact same alt as bandits 50nm away to spot them on radar. I can see them via datalink, but no radar contacts, so Jester won't lock them up. I've tried fiddling with radar elevation setting set to medium-low and low and also the range/alt settings, and it rarely make a difference. Then I have to decend to bogey alt, and the radar then sees them. :/ Imho, if Jester is set to auto radar elevation, if I'm head on with bogeys 50nm away, and I can see them via datalink on the TID, you would think Jester would maintain radar elevation so the ownship radar see them and he can lock them up... :/ So the question here is, am I dong something wrongs with the Jester radar settings? I usually tell Jester to go with 50nm scan distance and radar mode to TWS.

Yeah I know you must read to understand how the radar works. Yes, in the ground stabilize example that would answer my question. How do you tell jester to automatically dispense both chaff and flares? And what is the default behavior?

No. It does not describe Jester settings there at all.

Has this been implemented yet? Would be really nice to know when you can manouver off target...

I would also like a detailed explanation of every Jester command and their current setting (not all settings show what is currently set). Some are off course self explanatory, but some come to mind: What is the behavioral differences in setting radar mode to TWS or RWS or Auto? What does Ground Stabilize do? Jester CMS settings, what will Jester do? Only chaff? Or can he also pop flares? How to setup what jester does automatically?

I was hoping for TGP slewing without moving waypoint and/or proper use of SPI... And also creating new waypoints in cockpit. :( Who cares about warning sound priority.

I think it "should" do FAC if it sees targets and set via Enroute Task. I just created a simple test. A blue Hummer is set to Start Enroute Task FAC, a red unarmed utility vehicle is close by. Player in A-10C, contact axeman and it works as intended. Perhaps something set up incorrectly in your end? test.miz

Yeah, I was having so much fun with CBU-97 high speed low passes with excellent results. Now I can't zoom by at 550-600ft @ 500+ knots anymore :cry:No one figured out if we can change HOF still? Sthey just changed it to static 1500ft instead?

So is the AI changes only for non WWII planes or not?

This made a world of difference. Drop in CCIP, low level (anything between 600-1000ft), high speed 450-550kts ingress, level drop or very slight dive. Very effective!

This would be a much better implementation than the kneeboard solution some modules use today. :thumbup:

Yeah, offcourse they have SME's. I'm guessing they just put the default head position that far forward so us sim users won't have to lean forward in our armchairs all the time. :smartass: But I DO agree that it feels weird, like you're resting your chin on the dash. But I've also tried moving the default head position back in the seat, and I don't like that either because so much of the HUD get's obscured.

Yes. Much of the HUD elements would be obscured. I can't say exactly what a pilot could and could not see on the HUD, but they would have to lean forward to be able to see the full HUD. Just test moving your head back in the sim, as far back as you can, and you'll see that much of the HUD's elements will be outside the HUD glass boundaries. I'm no SME or have any experience with the real plane, I'm just paraphrasing what others have said in the past and it's apparently how it is IRL.

NAILS is not STT lock tone. SPIKE is STT lock tone. So, AMRAAM in SAM mode should then be just as stealthy as TWS lock according to this.

I don't think they will change it much. As I said above, moving back the default eye-point to where it should be in a "rested" seat position you won't see most of the HUD elements. If I remember correctly, I've read an official statement in some thread that it was defaulted this way because thats how it is IRL. If they change this, many will be upset about not being able to see most of the HUD, and they would have to lean into it to do that.

Ok. I might mention also that you can also do this in-game without config file editing. It's a feature called Snapview Saving. I don't know exactly how it works though, never used it. I also might mention, that doing what you want, will make most of the HUD elements not visible, you would have to lean forward to see all elements.

This is possible with a little config file editing. You can edit the file "..\Saved Games\DCS\Config\View\SnapViews.lua" to exactly put the default head position and angles (default is looking a bit downwards also) to what you want.

The TOP VOTED wanted feature a year-ish ago when ED asked us in a poll. Whats the status on this? Anyone heard anything about the progress on this?

Yes. I will require de-sanitize the lfs and io. Everyone who has used any of the Dynamic Campaign Engine campaigns (MBot and succeeding mods by users) has had to do this.

Surrexen I've got a finished framework for saving that you could implement. It's very simple and it will work as long as this mission is not dynamically spawning the red ground groups, but a complete mission with all red ground units in from the start... I've not looked at this mission that detailed yet so I don't know.

Thats the same bomb as FAB-500. Only with TV guidance. So FAB-500 have the exact same punch.

This I wonder too.

For the time being, I don't mind that we can set the bombs code in air, even if not realistic. As DCS JTAC or the scripted option (JTAC Auto Lase) cannot change code on demand. However, should RAZBAM chose to change this, I would prefer if it didnt require engine off. And I would politely ask that the other kneeboard options we have today that require engine off, to remove the engine off requirement. On ground and not moving is enough. So many times you just start up right away and then remember you wanted to change something... Can't be bother shutting it all down again.

I think 600W is what's usually recommended (or minimum I don't remember). I've got a 700W. If your computer's PSU can't deliver what your gfx card need, the computer will bluescreen or possibly insta-reboot. It won't manifest in FPS issues...

Uhuh. Ok. I see. I thought I heard in a training mission, or read, that the code on the bombs only could be set on the ground. So was expecting kneeboard. WIP perhaps? And the code on the TV page I thought was only for the LSS. Thanks!