Leaderboard

HQ-17A SHORAD 1.1.0 released! Changelog Version 1.1.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed display name Fixed dust and dirt effect position when moving Fixed issue with asset not engaging ECM enabled targets correctly

From Orbx on the Kola Peninsula. First word on it from them since last summer.

PGL-625 SPAAGM 1.1.0 released! Changelog Version 1.1.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed CIWS burst mode interval Changed FB-10A launch range at low altitudes Changed FB-10A performance Changed display name Fixed dust and dirt effect position when moving

New pic from Heatblur's Facebook:

Iskander SSM 1.1.0 released! Changelog Version 1.1.0 Added reload for 9M729 (600 seconds) Fixed reloading issue for 9M723 (600 seconds)

Type 052D Destroyer 1.2.0 released! Changelog Version 1.2.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed HHQ-10 guidance and accuracy Changed HHQ-10 launch range at low altitudes Changed HHQ-9B accuracy Changed display name Fixed issue with asset not engaging ECM enabled targets correctly Fixed the CJ-10 terrain following performance and max range

Type 45 Destroyer 1.2.0 released! Changelog Version 1.2.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed Aster 15 to launch at low altitude targets at closer range Changed Aster 15 to reduce accuracy Changed Aster 30 to launch at low altitude targets at closer range Changed Aster 30 to reduce accuracy Changed Phalanx CIWS to burst mode Changed display name Changed sound for Aster 30 launch Changed SAMPSON AESA performance

BTR-4 IFV 1.2.0 released! Changelog Version 1.2.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed display name Fixed dust and dirt effect position when moving

Modernized US Navy Ships 2.2.0 released! Changelog Version 2.2.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed SM-3 to intercept semi-ballistic missiles Changed display name Fixed AN/SPY-1 error preventing simultaneous target tracking Fixed AN/SPY-1 performance Fixed ESSM amount error Fixed ESSM anti ballistic performance Fixed the SM-6 AShM minimum launch range (25 nm)

IRGCN FAC 3.2.0 released! Changelog Version 3.2.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed display name

Type 055 Destroyer 1.3.0 released! Changelog Version 1.3.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed HHQ-10 guidance and accuracy Changed HHQ-10 launch range at low altitudes Changed HHQ-9B accuracy Changed display name Fixed YJ-21 max range Fixed issue with asset not engaging ECM enabled targets correctly Fixed the CJ-10 terrain following performance and max range

Make sure your fire mission is targeting a spot within the minimum and maximum range of your missile type of choice. The different circles in ME and F10 map will give you this information.

T-64BV MBT 1.1.0 released! Changelog Version 1.1.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed display name Changed unit name to avoid conflicts Fixed dust and dirt effect position when moving

T-84 Oplot-M MBT 1.3.0 released! Changelog Version 1.3.0 Added minimum weapon range indicator in ME and F10 map Added prefix to asset name Changed display name Fixed dust and dirt effect position when moving

Thanks, Beldin! Let me know if you get the landing spots sorted out. I can help if you need assistance. Just a lot of trial and error with the aircraft. LordVader9090, the Constellation already has liveries installed for all three versions of the ship. There are Liveries for Chesapeake and Congress as well. I plan to redo the Bainbridge as I don't like the way it turned out. The one thing about modeling is you learn something new with each model you create. Polu27 please ensure you don't have the older version of Constellation installed otherwise it should appear in the game. Great Video Pappy2!! Thanks. USS Blue Ridge - USS Mount Whitney NEWS. Their pretty much finished. I just want to ensure I didn't miss anything. Conducting Final Testing. I will be releasing her soon. Thanks for your patience.

https://twitter.com/Metal2Mesh/status/1644874374330175489?s=20

Soon!

Some A-7 development news (from FlyingironSimulation's discord). null

Fast alignment should take approximately 3 minutes according to the manual.

Any livery makers out there, we desperately need these assets done in desert appropriate colors. PLEASE!

I just wanted to thank you for your amazing work! I would love to see more ground unit's for the UK and the U.S.

Updated the ACM panel to be more realistic, thought I would take a photo of the 3 pieces that make up the desk mounted panels. They're all mounted to virpil long desk mounts. Getting close to being done with this. Still have to wire up the knobs and switches for the left gauges and the panels on the right sidewall panels. Really just want to play with it for a few months before I start adding stuff. Sent from my Samsung Chromebook Plus using Tapatalk

DSCG first with DMAS to follow, indeed.

Just wanna let you people know there's a new DCS module coming up. It's a Polish TS-11 Iskra (spark) Check out this Facebook group to find out everything about it. https://www.facebook.com/Ts11forDCS TS 11 STAGE 1 https://youtu.be/96wqdzJ4XCY If you wanna know more abaut TS-11 Iskra itself have a look here: https://en.m.wikipedia.org/wiki/PZL_TS-11_Iskra some real footage of Iskra https://youtu.be/UrLpLfr3gms https://youtu.be/sghIr9kmYW0

That's pretty much my issue. OP's code doesn't make any sense (see the random mix of group and unit as in Group.getByName(unit) ), and appears to be low-effort. I'm usually happy to help, but I'd expect a modicum of investment. Copying code from some AI Chat does not meet that requirement for me.

Alles schon gesagt, aber hier mal eine Beispiel-miz. Ein Bild sagt mehr als xx Wörter. Beispiel mit zwei Fahrzeugen später start.miz

I am beyond excited for this. So much so, that I have very little interest in the Eagle (which is another jet I'm fond of tbh) It was my favourite jet as a child growing up during the latter part of the cold war, and remains my favourite today. Heatblur can take as long as they want with it, I have faith that it'll be brilliant.

It's been fixed.

Refresh the page.

Als wenn du es ganz genau haben willst, wird das Triebwerk ausschliesslich vom internen Tank gespeist, und die internen werden durch die externen Tanks stets nachgefüllt. Somit werden die externen "zuerst" gebraucht. Wenn du weniger als 7200 lbs Treibstoff hast, sollten die externen Tanks leer sein, aber zur Sicherheit kannst du nachsehen, ob in den externen Tanks noch Sprit drin ist. Dazu nur den Fuel QTY Selector knob auf die entsprechende Position drehen. Dieser Drehschalter befindet sich zwischen den Beinen, rechts vom EHSI. Mit dem Treibstoffschalter auf NORM kannst du lediglich festlegen, von welcher Tankgruppe der Treibstoff gebraucht wird. Dabei kannst du zwischen NORM, Vorne/Rechts und Hinten/Links auswählen. Dieser sollte nur dann nicht auf NORM stehen, falls eine der Tankgruppe zu viel oder zu wenig Treibstoff hat und somit ein Ungleichgewicht herrscht.

If I could chime in on this topic for those that may be on the fence or possibly thinking about ditching on the Pico4 and selling or returning it. Currently have a G2 v2. Picked up a Pico4 a week ago. Watched every video and connected it wirelessly with Virtual Desktop just like all the videos said to. I'm on a 5950x, 128gb ram, 4090 and have Wifi 6 in the same room. Basically 1200mb up and down no drops on the LAN. Computer hooked in to gig ethernet directly, (side note, my internet service is actually DSL because I live in a rural area and only get 10mb/s internet downloads) But latency is where this is all at obviously with the headset on wifi. Fired up the Pico4, connected to wifi, enabled everything in the headset, updated and loaded up everything and just used the headset for a while. It ran fantastic, looks fantastic. Configured VD, got all the firewall stuff ironed out, and that runs excellent. Showing over 135-145 streaming bit rate, godlike, H264, Automatic Motion smoothing in VD, Sharpness at 75, the headset is locked around 900 - 1000mb/s. no dips or drops. I can't emphasize how well everything looks and runs in VD so far... I can run in a virtual environment and look at a big screen in front of me and my desktop runs as if I am on the monitor and not the headset. No felt latency. Good to move on to trying DCS now right? Here's where things get a little squirrely Fire up Steam from within VD like it says to do. Steam loads up, and shows the headset at 10ms latency. within the Steam house it looks fantastic and smooth. I am running 150% render resolution there and there is no option for steam motion smoothing anymore. Probably because that is being controlled on the VD side. in Microsoft OpenXR Tools the render resolution is also set at 150%. Time to fire up DCS in m-t. From what I understand DCS has native OpenXR support so I was wondering how this will go but everyone says DCS will run in OpenXR through SteamVR. If this is the case then when DCS loads I should be able to call up OpenXR Toolkit. So the game loads and I couldn't have been more disappointed at what I thought I saw. 25 frames and so stuttery and laggy that I almost got sick or fear of having a seizure. I came from a G2 that never dropped below 75 fps with everything dialed up to this? My first thought was I just wasted $500 and I'm going to send it back because I did EVERYTHING I was suppose to and I am locked at 25 frames? No way! I watched every video I can find and all these videos are claiming great frames and buttery smoothness with DCS and MSFS. So, I decided simply because the headset looks and runs so good outside of DCS that I will use up my entire return window trying to figure it out before giving up on it. To make this short story long I found the culprit to be in a very unlikely of spots. It was within OpenXR Toolkit. The setting for Shaking Reduction I had set for the G2 at -45% which was to help soften some of the jitters in the headset and when recording video. My settings for everything else were CAS, Override resolution to 2160 x 2160. No Turbo Mode, Motion Smoothing is no longer available to choose but when it was there is was always OFF. Framerate is locked at 92 and for some reason the option to turn off Framerate lock is gone so I have to go with what I had set for the G2. I turned the Shaking reduction to 0% and immediately the stuttering and shaking went away and my framerates ramped up to 45fps on the DCS home screen. Looks like the headset motion smoothing setting kicked in. Time to turn that off and see what this does. With 1 setting and turning off motion smoothing I go from getting ready to return it to I can't believe how nice it looks and runs between 75 - 90fps on any multiplayer map. Even on the deck of the carrier at night. A sweet spot that compared to the G2 for me is 5 times larger all around with a slightly larger FOV. I can move my eyes up and down and side to side and basically see everything clearly inside the cockpit. If I need to glance over to the RWR, or the fuel, or whatever I can do it with my eyes and not my head now. The colors, brightness, sharpness so far imo aren't as good as in the sweet spot on the G2 but I haven't got around to trying to tweak those yet. Basically inside of DCS the Pico4 in comparison to the G2 looks a little more dull in color and brightness but I think that can be adjusted some. I am by no means an expert on how to do this and what you are using as a setup will probably make things different in your situation but I can sum it up in a few basic points... --Latency is first and foremost. Get that as low as you can by any means, Cable or Wireless. Try to achieve less than 15ms steady --Get your computer hooked up to a Gigabit Ethernet cable from your router, using wifi to the headset, get on Wifi 6 802.11ax or whatever bandwidth gets up gig speeds up and down --Dial in the Virtual desktop settings and Steam VR settings --Then get inside DCS and play around with what works for you in OpenXR Toolkit. In my opinion you will absolutely need Toolkit to make this run well. --Start with motion smoothing in VD set to Auto and then experiment with turning it off. Some people like it on or Auto and locked at 45 but I tend to have it off if the frames stay above 75. I hope this sheds some light on those of you who are kinda of new to this and trying to make all this work inside of DCS. What I can tell you is dollar for dollar the Pico 4 is every bit as good as the G2 and in some ways better. It just goes about things in a different way. That's how the VR world is right now. There are no set industry standards for how to get from A to B. Kinda like Betamax and VHS. BlueRay vs HD-DVD, Cassette Tape vs CD (well, CD was the clear choice there lol). Eventually a standard will emerge and there will be plenty of times you will spend more time tweaking the headsets than actually playing the game you are trying to tweak them for. Welcome to my VR world. lol Hope some of this helps.

Nothing stops other vendors to implement Varjo quad views in their OpenXR runtime though. I am currently adding support for it in my OpenXR runtime for Pimax, so that hopefully it's usable with Crystal as well (and I'm making it an option to force foveated rendering even if the app doesn't ask for it, so users on Pimax won't even need the extra Varjo-Foveated software to enable it). All this stuff is relatively small development efforts, but for a fairly small number of users (whether Varjo or Pimax). I believe that's the excuse developers (both engine and platform) are hiding behind when not implementing these features. There probably isn't sufficient ROI from giving you better performance

Something went wrong with your embedded picture but i was able to open it as a link, yes this looks like the one ive seen in an E manual, but google results were confusing I was browsing different F4 phantoms versions, couldn't find one with AN/ARC-52, but interesting to see that radio was also on left in some variants

All those are fixed internally and will be included in next Open Beta update.

FYI, most mechanical radars can scan faster than they do during normal operation. However, scanning faster lowers your detection range by reducing your time on target (less pulses get integrated). I highly doubt the Captor-M actually scans at 333 degrees per second during RWS / TWS. Doing so would cut its detection range nearly in half. The benefit of this high scan rate capability (and AESAs) is 1. Less time lost in changing elevation bars and resetting of the raster scan 2. less time rotating the antenna face when in STT and during an aircraft roll 3. Track file revisits (main benefit of PESA and AESA). Which probably doesn't exist in the Captor-M in any mode except DTT. And this would only be during the motion between the targets. While on the targets (if performing a mini-raster) it would slow down again.

Yes our stuff will be updated as well but we are unsure if they will be 100% ready at map launch.

That sluggishness put me off too and i set the Viper on the shelf for a long time due to that. There seems to be a hardcoded deadzone. Everbody recommending negative curve but curves are horrible, because they are... well, not linear. Which comes with downsides but no upsides imho. So i cut saturation X lately and it works way better for me since that deadzone shrinks quite well. Jet becomes responsive with linear output compared to the varying output of a curve. Still would like ED to have a look at that. Even in the Hog with a loadout close to max takeoff weight i just need to put minimal pressure at, not even move, the stick to make small corrections. In the Viper, that deadzone makes one wiggle back and forth. It feels completely off for an agile jet with a FSS. Afaik the real jet got a deadzone so you don't go whoop with slightest pressure and i assume ED tried to emulate that? Bit offtopic, but i think it was worth mentioning. nullnull

I was pointing at this image not the whole thread

La FREMM DA Lorraine tire un Aster 30 !

The aircraft has been designed with SME input, we got what we paid for, a realistic representation. also, the tomcat is still in service and the typhoon does have a substantial operational history.

Actually, the chances are pretty high.

Absolutely, once I'm done with the first iteration of the AH-64 guide.

I know that many people prefer scratches and weathering. But I would like to be able to choose a new cockpit without scratches and scuffs and choose a skin from the factory. They will tell me that I can just choose a custom skin, but in fact it can often be prohibited in multiplayer p.s. and it would be nice to have several variants of green and white skins from developers, not even historical ones. Just to have a suitable skin for all the maps

Well, lets look at your points one by one: First, as you note, this official sub-forum is under ED and not a third party so that should be a clue, also they did say that it is Nick Greys favorite aircraft. Second, there are only two varients, the -3 and -5. I would bet that they will give us both since the differences are minor, just like they did with the P-47D -30 and -040. This is of course not counting the Night fighter and Photo reconnaissance sub-variants since night fighting and Photo recce are not a thing in DCS world yet, they would not add anything. Third, since we have not seen a single image yet, I think it is safe to assume that it is indeed at a very early stage of development, maybe still in the info gathering stage. Fourth, if they had anything else that they could share at this stage they would have. Does that help tamp down your hype?

Here’s a few screenshots from a few days ago. We flew a night mission against a enemy airport!

Greetings fellow simmers, Today I have come to nitpick a small, but prevalent technicality in the phraseology I hear used commonly in multiplayer servers where there is no local controller "staffing the tower," as it were, and the airfields are essentially "pilot-controlled." I say "pilot-controlled" as it is the preferred nomenclature that encompasses all sorts of non-towered operations. A "non-towered" field is a bit of a misnomer, since many airfields do have towers, but their towers do not always operate 24/7/365. They have published operating hours, and when the tower is closed, it doesn't mean the whole field is shut down. You just use the tower frequency as a CTAF, provided there is no discrete CTAF frequency published in the chart. This also distinguishes the term from "uncontrolled fields," since that is also not technically accurate. So if tower is closed, and there is no ATIS to designate which runways are in use, how do you know which one to use? The easiest answer is any one you like. In the real world, we can make use of things like the Airport Facility Directory (AFD), which has all the information that is too much to fit on a chart. This usually has things like the tower's operating hours (if applicable), traffic pattern altitude, preferred runways, noise abatement procedures, and so on. The preferred runways are also sometimes interchangeable with the "calm winds" runway(s). Winds are considered calm when below 5 knots in any direction. In calm winds, you could technically takeoff or land from any runway you wish. Of course, it is always best practice to choose the runway that most closely aligns against the wind, Sometimes this isn't possible, and you have to accept either a left or right crosswind on departure. So in these situations where the runway choice is ambiguous, which runway is "active"? All of them. But also, none of them. There are no "active runways" during pilot-controlled field operations. Active runways can only be designated by a local controller or specified in the ATIS message. At pilot-controlled fields, all runways can be "active." So when you say "taking the active" (where are you taking it, by the way?) or "clear of the active," you're not doing anyone any favors, because they don't know which runway you consider active. Always use the runway number when you're making a call that references a runway. It helps everyone listening on the frequency develop their mental picture of where you are in relation to them, and what is happening on the field, and in the traffic pattern. Always remember that pilots listening on the frequency might not be visual the field, or they are at the field but they can not see you, either because of ground obstacles or you're outside their field of view. When making your CTAF calls, pretend that you are talking to the blind. That is all. Thank you for listening to me quibble about this trivial thing!