DUSTY

Another MP CTD today - super frustrating :(

This is a pretty subjective topic I guess but I think the damage model has been really nicely balanced so far from my MP experiences. I've been shot at a LOT flying in the blue flag servers and have had everything from insta-death to various system failures and everything in between. From my experience, getting hit by a Radar SAM with a large warhead results in a large amount of damage/aircraft loss which seems about right. Then IR missiles such as manpads and AIM-9s/Mistrals have taken me out of the fight but I have been able to RTB with system losses and engine damage. Getting hit by two consecutive heatseekers usually results in the Tomcat going down. The only thing I've noticed is that the AIM-120 seems to struggle to mort the Tomcat. Once I took TWO hits from AMRAAMs and managed to RTB - albeit with massive damage to control surfaces. Overall my experience of taking damage in the Tomcat has been a lot of fun and I'm always eager to push the limits in online play.

I just had this problem for the first time tonight. Multiplayer in the Blue Flag PG server, got shot down by a Hazard Perry (sigh) then couldn't get the right engine started. Left and rejoined the server to no avail.

Had three crashes tonight when playing MP. Restarted PC between the second and third crash.

It's slang for making something less lethal/potent/effective/good etc

Thanks Super Grover, you're a champ!

So in the change log: Since this update I've done most of my flying in the Buddyspike Blue Flag PG server and I've noticed being spiked by hostile HAWK SAMs but when they launch there is no launch indication from the RWR like there used to be. Is this to be expected or has the RWR been 'nerfed' a little too much? Cheers!

Screw it, I'd pay for a -D anytime! Better radar, JDAM, DFCS and better resolution for that LANTIRN! (I think?)

Interesting vid, was that an F4? And that's really good news about the update! :D

If you're heads down looking at the TID during a WVR dogfight you're doing it all wrong, sorry man! I play on Blue Flag a lot and have never had this issue and do quite well with the Tomcat vs 18s and 15s etc. I select jester to scan 50nm ahead when it's about to get hectic which gives me good SA as to where to point the nose. Then I switch to PAL if I'm low on SA and I know a hostile is within 15nm and if that doesn't work it's time to flow out and have another crack at it when you've built your SA back up.

Not sure about slewing axis but to get started it's as simple as putting the default.lua in the path specified in the instructions. Easiest mod to install ever!

Same here.

Yep +1 It's the elephant in the room.

Keen!

It's a long running DCS bug and it frustrates the living hell out of me!

Thanks for the replies! I'll have another crack at it! Patience I have... sometimes. For all other times I have CTRL+Z :music_whistling:

Can someone help me with the logic of the LANTIRN OPER/STBY (Unstow) switch? I accidentally pressed it when my LANTIRN was working fine and it appeared to kill my pod completely. I couldn't get it to come out of 'NOT RDY' after I toggled the switch. I even toggled the power to the whole LANTIRN and waited 9min then hit the 'OPER/STBY' keybind and waited the applicable 30 seconds + and nothing. Would not come back to life. Any ideas?

Pretty sure this is an ED bug and not a HB bug. https://forums.eagle.ru/showthread.php?t=229985

No you need manually ask jester to select which datalink host you want from the commo rose

NICE! :megalol:

Hahaha ^Me to my human RIO all last night.

I'm sitting here with a very sore butt because I have been glued to my pit all day flying the Tomcat. I just wanted to say thank you to the team at Heatblur. What you have done for the community with the F-14 is nothing short of amazing. Jester is a work of art. Sure there are some quirks and kinks to be worked out but what an absolutely awesome way of tackling the 2 seat aircraft concept in DCS. My wingman started wetting himself when jester told him to 'use the force' after he struggled for a while to plug into the -135. I'm lucky enough to have friend who is acting as a dedicated RIO and this whole evening we have been in stitches as we have learned to fight and fly the tomcat as we work together. I nearly fell over when my RIO started blasting the Meteor soundtrack in the jet. I'd seen the references to a walkman but I didn't realise that it was actually implemented! My last flight entailed two very satisfying kills against Mig23s over the desert - there's just something about the 'clunk-clunk' of the missiles coming off the jet. As I was flowing out of bad guy land down on the deck I over-g'd the jet avoiding a dune that came out of nowhere. Next thing I know I'm climbing into the sunset with an AHRS caption and all my heading tapes spinning. A big dumb grin spread across my face, basked in the warm red glow of the F-14 cockpit flood light. Bless this thing. Thanks again to the whole team at Heatblur for providing us with something that will give me and my squadron mates hours upon hours of entertainment and joy. I am very keen to see this module mature along with the wider DCS platform. Cheers!

When WYPT is boxed the waypoint name is obscured by numbers.

Is this only me? Here you can see the Canopy goes transparent when the haze is directly behind it: Just looks wrong here. Zoomed out and at high altitude it looks much better but ships still appear as though they are in front of the haze when they should be 'inside it'.

Can someone help me? I'm running a i7 4770 which i understand has 4 cores and hyperthreading. What should I set my affinity to in the autoexec.cfg? I've tried process lasso and using task manager to get DCS to use all cores and I still get awful stutter and freezing.