Leaderboard

@NineLine @BIGNEWY Hello gents, Could we ask the development team for news on what the future holds in store for the WW2 Asset pack? In particular the status of some items originally slated for inclusion: Bf 109 G-6 Hawker Typhoon B-26 B-25 B-24 Avro Lancaster Also the likelihood of any of the following items to potentially see inclusion: WW2 era Cargo/Tanker Ships Destroyer Class Ship Minesweeper Class Ship WW2 era Mobile AAA vehicles WW2 era Fuel Trucks WW2 era Ambulances WW2 era Fire Fighting Vehicles Eastern Front WW2 Assets Runway Lighting Object for defining runways during twilight operations I appreciate that we've had a fair few additions that were not originally planned but I think most of us here would agree that those items listed above would massively help to make the WW2 Asset Pack be more usefully complete.

We are still planning for a patch today the 28th Please remember the rules when posting here, they can be found at the top of the page thanks

Dear friends, first of all, many thanks for having supported us during all these years! Your words have been a strong inspiration for us and have encouraged us to try and make the MB.339 as detailed as we could make it. However, we are conscious that this will not be perfect, and due to its complexity, there is the possibility that new bugs or defects will be spotted: rest assured that development has not stopped and we will continue working to improve the plane. We believe in a complete, honest and transparent communication with our customers, so here is the list of bugs and improvements which we are working on at the moment: Missing features: Flight Director Gun Camera Wheel chocks Known Issues: The gunsight MILS settings tumblers should be discreet, now it is possible to set in between steps. Breakes on controls indicator window always ON Repair does not replace used/overheated/broken battery Missing many key binds Easily flyable with one wing if the aircraft is fully loaded of weapons Flaps do not have a collision model MB-339 Rear canopy does not break from ejection When replaying the trackfile the view position in the rear pilot appears too backwards so that it is covered by the pilot model Wingtip damage missing It is possible to eject in either seat and still control the aircraft if you are not solo. You cannot swap to the other seat, but nonetheless control is still possible. Also, the other guy should probably eject too if you can't swap seats to control the aircraft. (Even though the seats aren't linked) AI - Damage model might be over performing Damage to flaps has no effect on maximum speed straightline or stall speed (clean) The release is now imminent and we are really excited for our debut on DCS World as a third party developers. We look forward to your feedback and encourage you to provide constructive criticism so that our product meets the highest quality standards. Thank you! IndiaFoxtEcho Visual Simulations

Soon to be added to the pack:

The issue has been identified and a fix is in the making.

IndiaFoxtEcho MB 339A/PAN MLU pre-release status update: & known issues list:

Good morning community! i wish everyone a relaxed friday - please enjoy the day whether the patch arrives today or not. The bigger the patch the higher the dissapointment for any delays. So this patch must be really big ED has always delivered, not always the day we have wished for, but we all have been very happy at the end. So keep on being patient… You can do it

Hi all, we do have an issue with shadows that may be affecting FPS If the shadows for terrain objects is set to "off" the issue occurs. It doesn't happen with either "flat" or "standard" shadows on. Please try adjusting shadows settings to see if you notice a difference. We will of course patch a fix as soon as we have collected enough data for what needs to be tweaked. thank you

The only reason I'm not acting like a toddler is because I have ice cream. But if the update isn't out tomorrow I'm going to have to buy more.

So much entitlement and should have, could have, would have here. Thankfully, the majority of people who are silent, have understanding and patience enough not to act like a bunch of toddlers.

Ka-50-3

I'm sorry to say, but this would happen sooner or later. Let's face it, it's an abandoned third-party software.

Buying an Italian plane (module) while first time in Italy is a totally new experience.

So, no October update for the Syria map despite promises from @MAESTR0. I'm pretty annoyed, like all of us will be, that after all this time, we are no further forward. After all the false hopes, UGRA have failed to come good.

For me it will be the Hornet cold start in Persian Gulf off Supercarrier. Unfortunately it will have to be hopefully next week, have to get clearance from my surgeon after my spinal surgery. So I will be watching your guys posts in here with great excitement.

Cairo.

I can see why you guy's did away with the roadmap

you have given your feedback, but we have no plans to change how we do patch days. When we plan a patch we like to keep you all informed, its that simple.

This is Hornet Ready on the ramp instant action mission in 2.8, with RTX4090, Ryzen 5800X3D and Reverb G2. This is the same spot in 2.7 I made a week ago an posted on the forums, using the same hardware and settings: Compared to 2.7, the GPU frametime went up by roughly 10%. CPU frametime went up by roughly 30%. Yay. Notice the different look of shadows in 2.8. In 2.7 I used terrain object shadows set to "flat". Terrain object shadows options "flat" and "off" do not work correctly in 2.8, which may be the reason for the performance impact. See: https://forum.dcs.world/topic/311147-strange-behaviour-of-shadows-on-28/#comment-5074052

Halos are here.

Not broken here. Secondary shadows apply only to supercarrier. PG looks damn good, and runs super smooth aswell. Night lights are stunning!

The VR optimization was mentioned in the newsletter on 14th October as following: "The Weather System includes optimization for VR, and we are confident that this will result in a more stable and smooth experience."

https://www.digitalcombatsimulator.com/en/news/changelog/

Launch Video

The Mirage F1

I thought I had clicked on the patch notes discussion thread, but I must have clicked on the meaningless post and speculation thread.

Also available now in DCS Web page (Downloads-Texture templates). https://www.digitalcombatsimulator.com/en/downloads/texture_templates/mirage_f1_template/ I will soon remove the link in my first post.

Да блин, хоть че-то красное - уже приятно. Лишь бы от ЕД.

That's what you say after the update has been released, not before!

The only reason I want 2.8 to come out is to get my hands on the MB 339! Good honest developers must be repaid with sales, not words First day purchase for me, and will stay standby for the Gina! p.s. Please work on a Template (paint kit), I would love to make a skin with my squads colours....

Dear friends with skinning perversion, this thread is dedicated to you! [emoji2770] You can download the paintkit from the following link: https://www.mediafire.com/file/cebqrzoqu02ofb3/TEMPLATE-MB339-4K.rar/file Fuel tanks and smoke tanks template: https://drive.google.com/file/d/1WhuwN447A5rAgnB5ALw3jAoDVHC3HryW/view?usp=sharing If you are a GIMP user, we recommend to download the development version from here: [/url]https://www.gimp.org/downloads/devel/

UPDATE 2024-07-08: Added Afghanistan Map Link to download the mission: https://www.digitalcombatsimulator.com/en/files/3326657/ Hello all! DCS 2.8 brings to us a new BFM model for AI aircraft. In one word it's: AWESOME! I've put together a simple mission for you to practice your BFM skills against the re-vamped AI. This mission lets you choose your aircraft.... Once in, you can spawn a variety AI adversaries. Each one will spawn on your nose, 7 miles and heading directly towards you. You can choose to spawn one aircraft, or spawn several at a time. Once you've defeated an enemy, you can spawn more. You can also jump into another jet if you'd like to continue the fight. I hope you enjoy it! Use it to get good.

Dear all, unfortunately this patch around there is no real changelog for the Viggen. Our main focus was on updating it to work with the 2.8 update, which still required substantial input from our side. We would still like to kindly ask you for your feedback, as such major version progressions always can bring issues with them, although we hope that everything should work as it did during testing for 2.8. Thank you! To be noted: with 2.8 it seems that the parking brake issues has been fixed. This was not an active fix on our part, but came about due to the changes in 2.8 and is a positive by-product our testers discovered. If you experienced any issues with the parking brake + rudder pedals, please try if it now works for you as well. Thank you! In the meantime we have been focusing on updating the damage model of the Viggen in the background, which we hope we can bring to you the coming patch, including more other fixes and updates of course. Thank you all for your very kind patience.

This so much. Why, just why would you do this. Cockpit scripts are absolutely neccessary. IC the specific files that allow cheating, not all of them because we need to edit some of them!

The MiG-23 should in no way return a Mode 4 response to my interrogation. Let's imagine it has NATO IFF equipment built in (DCS currently abstracts this), it would not reply in Mode 4 to an incorrect interrogation relative to its own codes. It would stay quiet to not give away its position. EDIT: (as you've basically said yourself)

Yep, no Normandy 2 for me either until this is fixed. Honestly, it's ridiculous. Even @MAESTR0 has said it is a 1 line fix.

hope i can fix it by the end of this year nov and dec are months for vacation

hahahaha. there is for dev test purpose but disabled. we are still trying to find more hmd info, like how it displays, but so far unfortunately like regular GBU, once you hear beeeep, then you can drop, the indicator line also starts to change from dot line to solid line (similar to gbu54) it's range is around 20km

I see no VR optimization comment

I did get your point, even if I did not respond in the way you wanted me to respond.

There is or at least was a mod around that adds a lot of star wars stuff to DCS. Just google for DCS World Star Wars mod and you shall find it.

It is delayed until I come home from work, otherwise you rascals would crash the server. Ok guys, what is the first quick mission and plane you will fly 2.8 at?

Campaign is complete, and pending post 2.8 update checks, will be submitted to ED in the coming days.

20+ years of IT experience has taught me that the Friday release ban relates to not wanting a production outage or major issue over the weekend and not having people available to fix it... That isn't the case with DCS, people can always roll back, it's a beta, get it out there when you think you're done, waiting over the weekend isn't going to achieve anything...

Template is already available in the FAQ post :) Inviato dal mio ASUS_I005D utilizzando Tapatalk

Hi all, please play nice with each other.

SET COMMAND WITH VALUE 10009 <value> value = 1 disables Jester LANTIRN auto designate value = 0 enables Jester LANTIRN auto designate (default) SET COMMAND WITH VALUE 10010 <value> value = 1 silences Jester value = 0 Jester will talk again (default) SET COMMAND WITH VALUE 100011 <value> value = 1 disables Jester value = 0 reactivates Jester (default) SET COMMAND WITH VALUE 10012 <value> This is a special command with which you can force Jester to track a specific target using unit name. Since SET COMMAND can only accept numerical values >= -1 and <= 1, we use the following rule: value = 0.01 will track unit named LantirnTarget01 value = 0.02 will track unit named LantirnTarget02 ... value = 0.99 will track unit named LantirnTarget99 value = 1.00 will track unit named LantirnTarget100 value = 0 will resume Jester state to normal operations SET COMMAND WITH VALUE 10013 <value> Another special command but this time Jester will track zones. value = 0.01 will track zone named LantirnZone01 value = 0.02 will track zone named LantirnZone02 ... value = 0.99 will track zone named LantirnZone99 value = 1.00 will track zone named LantirnZone100 value = 0 will resume Jester state to normal operations Commands 10012 and 10013 are exclusive - when Jester is tracking a unit using command 10012, activating command 10013 will force jester to stop tracking that unit and start tracking a zone, and vice versa. Using value = 0 in either of the two will stop tracking both units and zones. 10014: Jester will designate manually what is under the lantirn cross. 10015: - tune AN/ARC-182 to a selected channel. As the value pass: 0.XX where XX is the two-digit channel number 10016 - tune TACAN channel. The value should be constructed using the following guide: s0.XXXY, where s is an optional - sign - use negative values for A/A and positive for T/R XXX is the three-digit channel number (remember about the leading zeroes for channels lower than 100) Y is 0 for using X-mode, and 1 for using Y-mode. so: 0.0630 is channel 63X, T/R -0.0081 is channel 8Y, A/A 10017: DEST knob 0.1 - WP1 0.2 - WP2 0.3 - WP3 0.4 - FP 0.5 - IP 0.6 - ST 0.7 - HB 0.8 - MAN 10018: select waypoint to enter coords from a trigger zone (this command does no action in the cockpit) 0.1 - WP1 0.2 - WP2 0.3 - WP3 0.4 - FP 0.5 - IP 0.6 - ST 0.7 - HB 0.8 - MAN 10019: enter coords from trigger zone for the waypoint selected with 10018 (if no selected, WP1) 0.01 - WaypointZone01 0.02 - WaypointZone02 ... 0.99 - WaypointZone99 10020: WCS switch 0.1 - OFF 0.2 - STBY 0.3 - ON 0.0 - return to automatic 10021: run RWR BIT 10022: TID range knob 0.1 - 25 NM 0.2 - 50 NM 0.3 - 100 NM 0.4 - 200 NM 0.5 - 400 NM 0.0 - return to automatic 10023: Jester Eject 10024: STT target: 0.00 - Stop force STT track 0.01 - AirTarget01 0.02 - AirTarget02 ... 0.99 - AirTarget99 10025: break lock 10026: weapon station state 0.xy x - station number (1-8) y - state: 0 down (safe), 1 up (selected) 10027: weapon wheel option: 0.10 - MK-81H 0.11 - MK-81L 0.12 - MK-82H 0.13 - MK-82L 0.14 - MK-83H 0.15 - MK-83L 0.16 - MK-84 0.17 - LAU-10 0.19 - CBU-59A 0.20 - CBU-59B 0.21 - CBU-59C 0.22 - MK-20A 0.23 - MK-20B 0.24 - MK-20C 0.25 - MK-45 0.26 - GBU-10 0.27 - GBU-12 0.28 - GBU-16 0.29 - GBU-24 0.30 - BDU-33 0.31 - TALD 0.32 - SUU-25 10028: ATTK MODE knob: 0.0 - CMPTR TGT 0.1 - CMPTR IP 0.2 - CMPTR PLT 0.3 - MAN 10029: DLVY MODE switches 0.xy x: 0 - STP, 1 - RPL y: 0 - SGL, 1 - PRS 10030: DLVY INTERVAL 0.xy x: first roller y: second roller 10031: DLVY QTY 0.xy x - first roller y - second roller 10032: MSL Launch 10033: Radar azimuth -1 to 1 10034: Radar elevation -1 to 1