uri_ba

Hi all, I'm trying to find the angular resolution (accuracy/error not sure how you have it implemented) simulated for the Pod in the Viggen. I Know it's a very specific piece of information but that is what I'm looking for DOes anyone knows where I can find it? thanks! uri

Yes, and below that point engine will be in cut-off

Old school Group.activate() works as expected. It's just emissionOn that causes the issue

IRL there is a cutoff point, you need to phisically pull a release lever on the throttle and tilt it up to move it out to IDLE. You also need to do the same to shut down. For AB you lift the throttle up without depressing the lever to clear the stop there. So yes, the pilot presses a key you can program the cutoff of the WH to be the cutoff and then you just pull it out of the detent to start.

When running on a dedicated server, using the new emiiterOff/On functions. HARM is not showing radars (in HAS mode) nor will the missiles home in PB mode. When running mission as offline, or hosting it myself. no issues. when running mission on a dedicated server and connecting - no joy. I don't have the Hornet to test. But in a different mission where this was discovered hornet had no issues. I've added a hornet to the mission for testing just in case. I could not save a track, but I'm attaching the test mission. 2xSA-6 sites are emissions off at the beginning. they will turn on their radars after player passes WP1 by about 6nm towards WP2 Both sites show up on RWR and will launch on you, but HARM seeker will not pick them up. In addition, there is also an SA-2 site in WP3 (which is on from the beginning). the P19 assigned to that SAM is detected on HARM, while the FanSong is not even when it wakes up and shoot at you (I assume it utilizes the same function to turn on/off as the emitter lua functions expose behind the scenes). further more, if at this point, once they are activated and "invisible to HARM" you log off the server, then reconnect to it, SAMs appear. (but not if you go back to spectators and reconnect to your slot). SA-2 FCR will not show up (as it's still using the same On/Off state change). This is seems to be new to 2.7.0.5659 as it was working correctly on 2.7.0.5118 Thanks, Uri HARM_dedicated_bug.miz

Same-ish performance on "normal" cards, and better utilization of cards with 12gb+? That is a possibility

Well skybox is definatly showing I've updated Drivers and PrecisionX. looks like something there got screwed up as my card power limit dropped to 50%... bringing it back up to 108% card's maximum broght the FPS back up most of the time. when you hug a cloud it still drops to 40. but waay better now.. Anyway, still waiting on 3080 to be back in stock somewhere in a reasonable price... and balck was the Shader Mod way of things. this seems different.

After runnnig a full repair (I had stock install anyway, so nothing has changed). removal of Metashaders and FXO. I'm still seeing 40fps (down from 60). more bizarre, I had always had 120FPS in the menu now it's fluctuating between 100 and 120. I've tried my settings. as well as VR preset with now difference. (Viper Caucasus Free-flight and M2K Caucasus Guns, guns, guns missions were tested - I just spawned in and that's what I got) as for the blue around the mask, it seems to be the skybox and base water. that's why it was blue. Only folks with 3090 seem to report increased performance, so I wonder if it's a VRAM issue.

For me in an unmodded Install with 8700K & 1080 performace tanked. from 60fps ish (Index running at 120Hz) I'm now seeing 40 on free flight missions. (in addition to flickers and aliasing of the clouds). I've touched nothing in the settings. I'll try reset FXO/Metashaders and maybe lower the clouds a bit more. is there a way to make sure there are no leftovers of the shadr mod installed? because on login I got a blue mask like the black one shader mod used to make.

Unfortunately it's one missle per station and takes away an important hardpoint. No wonder they never flew with them an A-10 style double launcher would have made it easier to bite the bullet guess we'll need competent CAP around is there a list of "common" loadouts? also, no MER/TER for GBU-12/16? That's disappointing. that's TRAM loadout. What about SWIP?

SWIP will be the better option for DCS. in the current MP arena, lacking any AA ability (no gun and no AA missiles) so having EVERY AG weapon option is preferable. for era specific missions, I'll trust mission builders to limit loadout and availability.

Blesimtek had the F-4E slated after the Mi-24P. but that all got jumbled when they were acquired by ED two years ago. so I don't think HB will be picking it up

will the campaign be available as COOP? or is it offline only? going over this with my PLT sounds like fun :)

when the RIO arms the Aircraft, none of the weapons work. the PLT shoud set the loadout.

I've just noticed that the Tactical commander gets exact position of enemy radars without any friendly units in visual range. I have a yest mission for a script I'm writing where I have a few c130s flying around at 20kft south of kobalety. Imidiatly i have exact positions on the f10 map for EW radars 60nm away. It makes no sense to me. Being aware of it's presense sure. Exact position if a unit is within visual range and with LOS, sure. But based off an RWR chirp? Not really possible.

Fictional Israeli Airforce Livery, based on the 144th "Phoenix" Sq. mid 90s Livery. First of all apologies, you requested one skin submission, but these are twins and I could not bring myself to separate them Both Liveries are originally built as an F-14B Livery as will be explained below. However, in order comply by contest rules, the Gray Air supremacy Livery is submitted as a F-14A-135-GR Livery, while the Desert camo is submitted as F-14B. In 1994 the IAF received a squadron for USAF surplus F-16A/Bs, they remained in their original USAF gray for a few years slowly being repainted to the "trademark" IAF desert camo. In the fictional world this Livery exists, the IAF received ex. USN F-14Bs. and some beauty shots: I've tried my best to try and recreate the correct "Vibe" so I've created a few extra surprises in the cockpit. these include (but not limited to): * IAF helmets similar to what was used in that time period (1985-2000) * flight suit patches (in the spirit of early 2000s "patching standards" for the IAF) * ranks and name patches omitted as it is customary not to fly operational sorties with them. and one last bit if trivia, actual photo taken by the 144th circa 1996, this was my true inspiration for this livery (check bort ). Official submission file with contact details was sent to @ensamvarg via PM as requested for all you other folks interested, it's available in Userfiles

Any chance anyone has enough LUA skills and time to set us up with YT chat as well?

I've played on a 50+ slot server last week. i flew a BB off the Stennis. I've had several successful startups after a deck misshap (Non SC and no external views. I had been disconnected bfrom CAT on full power). Anyway, I have been shot down by AIM-120, ejected and respawned in the same slot before aircraft crashed into the ground. When respawn, GC will not connect electrical power nor the huffer. So I was not able to startup. I've tried exiting and retaking the slot. I've tried another slot on a different carrier. And even tried disconnect and reconnect to the server (hadn't tried restarting DCS). Unfortunately i only have a video of this (I was streaming) . Have any one encountered anything similar?

Initially 54As were only reserved for fleet defence missions. CAP were flown with 4*7+4*9. Only the 90s did the 54Cs were cleared for Tactical engagement (i.e dogfights). Currently all 54 varients are pretty much the same in respect to tactical engagment. However, the C had much better processors. I have no evidence but I assume that the Cs had better guidance logic allowing it to have better energy management in flight and better logic in terminal guidance. (In additional to better ECCM and probabaly much smaller doppler gate and better target re-aquesition)

Flight sims can be misleading you into thinking somethings are working in a specific way, where the mechanics in the Real world dictates something else. You really need to look at documentation to avoid those pitfalls. For example flaps, lots of people insist on misusing in this bird. Flap handle Is a lever with long travel, but it's not an axis, there is only up and down. (No partial flaps) And You are not ment to use them over 225kts or over 3Gs or so. Manuver flaps do their thing automatically you can force them with DLC. But everyone keeps forgetting that the DLC is a self centering axis. When you let go it will return to center.

AFAIK, it's a frame limit not an engine limit. Its temperature limit for the canopy and other frame componenets. Engine itself is fine. Both the -229 and -129 are used by the F-15E which has higher top speed. In some contdtions the airframe can give you more then it can handle. Engine limitations do exist, like engine RPM must remain above some value when supersonic. You can pull throttle to idle, but engine will be maintaining near MIL till speed drops (engine controller logic, just like nozzle maintaining combustion chamber pressure)

:thumbup: Missed that one :)

When switch in "Preset" radio is in guard. When on "guard" radio accepts presets.

I guess I'll need to record a track and play it back twice once in VR and once in "2d" with same settings and see how much of this is due to VR being enabled.

it must be a VR thing then. because this is my experience with HIGH vis range (I bumped it up from MED to test) but I've seen it also in Caucasus map. so maybe it's a "VR optimization" thing?