Patch notes discussion June 2023

[SkateZilla]

3 hours ago, MAXsenna said:

 

 

I believe SD meant that as soon we get Vulkan, DX11 will be depricated, and we'll never see a DLSS compatible DX11 version.
Why would we, when an official video with Vulkan and DLSS were released? Unless I'm totally wrong, and I wouldn't mind being proven such at all.
Wouldn't it be double the work for nothing if they work on DLSS on both DX11 and Vulkan?

Cheers!

Sent from my MAR-LX1A using Tapatalk
 

 

 

I wouldn't waste time speculating,

Yearly Beyond videos can showcase content in the immediate pipeline as well as in the late in the year pipeline.

DLSS 2.0 works on DX11, DX12, Vulkan, etc.



 

[MAXsenna]

 
I wouldn't waste time speculating,

Yearly Beyond videos can showcase content in the immediate pipeline as well as in the late in the year pipeline.

DLSS 2.0 works on DX11, DX12, Vulkan, etc.



 

Great! Thanks!

Sent from my MAR-LX1A using Tapatalk

[Leutnant_Artur]

How is the DTC progress going?

[BIGNEWY]

Early Access Launch of the DCS: F-15E by RAZBAM

DCS: F-15E Top Tips

• Radar channels are modelled, so if in MP all are close together and on channel A, then they will see interference that looks like jamming on the radar - they need to deconflict channels.
• PACS - All none smart weapons have to be manually input into the jet on each in game rearm. 
• Mic switch needs to be set to "on" to communicate with ground crew - default it is off.
• A/P button on the UFC keypad not only shows the autopilot menu, but also enables autopilot. If they want to just look at the menu, then use the UFC PB9 from the main menu.  (This is correct behaviour)
• LANTRIN pod will prohibit laser use above 25kft - intended behaviour.
• LANTRIN Pod has only FLIR function, no CCD/TV.
• There is an option in F-15E special options to set how many processor cores are used for the radar - adjusting this will help with FPS issues.
• Cold Start - Apply the parking brake before setting INS to ALIGN, otherwise the process may fail. Avoid rearming whilst alignment is in progress.

DCS: F-15E by RAZBAM - Known Issues

• Bombs dropped in AUTO mode can land long of target for wings level release. It is recommended to do a dive bombing for improved accuracy.
• CBUs can open prematurely, specially if dropped above 1500 ft AGL
• HUD Repeater in MPCD sometimes not visible
• MFD exports not yet implemented
• Volume control for TEWS & TACAN WIP
• WSO HOTAS commands WIP
• AA/AG Gun piper aims high.
• Some items on UFC not synced between front and back cockpit - WIP
• Cockpit Mirrors not symmetrical
• Rear cockpit MFD displays cannot be programmed.
• It is not possible to change the GBUs laser code with the kneeboard.
• Sometimes PACS does not automatically recognize a weapons load. It must be manually entered.
• GUARD is not monitored when selected in the Presets and active mode is Manual Frequency
• Using AG Radar HRM mode can cause a drop in FPS during the image digitalization phase. This depends on the running computer specs.
• Very Rarely, when using AG Radar, DCS will freeze for a second while checking the terrain. This depends on the running computer specs.
• It is recommended to use the AG radar with DCS MT.
• AI wingmen will attack with gun only despite having more relevant ordnance.
• Dumping fuel will cause fuel totalizer to read 0.

DCS World

• New IA mission for Sinai Map: MiG-15bis, F5E, and Su-25T
• MT. Shaded 3D models in ME and Encyclopedia
• ME exits without Save prompt when closing Encyclopedia with a double-click - fixed
• MP. Server. Missions lists are now separated. MP mission launched from ME would be always shown as a single one in list while ordinary mission list accessible from MP menu will not be purged
• Train horn sound fixed
• Cancel button not working in game options/system - fixed
• ME. Egypt. Historical database checked and corrected
• ME. The crew's radio is enabled 
• MANPAD units will not have smoke damaged effect after being hit
• Fixed several crashes in certain situations
• NS430 Persian Gulf crash on zoom out to 200 nm - fixed

DCS: Flaming Cliffs by Eagle Dynamics

• Su-33. Heavy sky mission 20, Immobile Kuznestov makes takeoff impossible - fixed
• Fixed Sinai QS missions
• Fixed radio communication in the IA mission F-15C
• Fixed CTD when leaving Gazelle slot then spawning in a FC3 aircraft

DCS: A-10C II Tank killer by Eagle Dynamics

• ARC-210:Incorrect display of the symbol "," on comm page. -minor: comma will also be filtered out from ARC-210 preset name

DCS: F/A-18C Hornet by Eagle Dynamics

• Fixed: Using SEQ UFC wp delete function causes crash

DCS: Mi-24P Hind by Eagle Dynamics

• Fixed: Searchlight multicrew desync
• Fixed: Petrovich AI switch targets in the loop sometimes
• Fixed: Fuel shut-off valve sound

Campaigns

DCS: F/A-18C Inherent Resolve Campaign by Looking Glass

• Just one mission and a new PDF

DCS: AV-8B Hormuz Freedom Campaign by SorelRo

• Weapons loadout changed as per latest AV-8B update for mission 12 and 7 and briefing text changed for mission 3.

[VR Flight Guy in PJ Pants]

502 Error is back!!!

But can still download the SE -- for now! ???

Edited June 22, 2023 by VR Flight Guy in PJ Pants

[ricktoberfest]

So what fixes/changes made it in that aren’t in the patch notes?  There must be some- there always is. 

[Artax]

no fix for ECM bug??? Wtf it should get an hotfix....

[schurem]

Used to be this guy on reddit who'd run a diff on all game files to make real changelogs. Autism as a superpower!

[dburne]

So I am sure very dumb question on my part - what is deal with F15-C also showing in controls menu in addition to F15-E?

[tripod3]

B-1 and B-52H new model is here or not?

[Tom Kazansky]

7 minutes ago, dburne said:

So I am sure very dumb question on my part - what is deal with F15-C also showing in controls menu in addition to F15-E?

Flaming Cliffs 3 owner?

[Artax]

Anyone else noticed a big drop in fps, even on old planes like the f16?

[dburne]

28 minutes ago, Tom Kazansky said:

Flaming Cliffs 3 owner?

Hmm yeah that may be. I think I purchased it quite some time ago and never got around to using it.

Edited June 22, 2023 by dburne

[Hiob]

1 hour ago, Artax said:

Anyone else noticed a big drop in fps, even on old planes like the f16?

No. Are you by any chance still on legacy after the update instead of MT? No restart after Update?

[Japo32]

Is it slower in loading? Of course after the first load the shaders and constructed again.. but I mean that second or third time. Also a friend noticed it.

[einarabelc5]

On 6/8/2023 at 2:01 PM, [WF]-Templar said:

shockingly bad prep ED, shockingly bad!

 

Thanks for keeping us abreast anyway but a great reminder that you own the modules and that we essentially rent them.  That's right peeps - no ED, no modules.

 

Didn't we go through these DRC woes already with Sony a couple of decades ago? Lucky you, my F-15E module didn't even show up. The whole DRC system needs to be revamped and though out from the ground up, I've seen other issues as well.

12 hours ago, BIGNEWY said:

Early Access Launch of the DCS: F-15E by RAZBAM

DCS: F-15E Top Tips

• Radar channels are modelled, so if in MP all are close together and on channel A, then they will see interference that looks like jamming on the radar - they need to deconflict channels.
• PACS - All none smart weapons have to be manually input into the jet on each in game rearm. 
• Mic switch needs to be set to "on" to communicate with ground crew - default it is off.
• A/P button on the UFC keypad not only shows the autopilot menu, but also enables autopilot. If they want to just look at the menu, then use the UFC PB9 from the main menu.  (This is correct behaviour)
• LANTRIN pod will prohibit laser use above 25kft - intended behaviour.
• LANTRIN Pod has only FLIR function, no CCD/TV.
• There is an option in F-15E special options to set how many processor cores are used for the radar - adjusting this will help with FPS issues.
• Cold Start - Apply the parking brake before setting INS to ALIGN, otherwise the process may fail. Avoid rearming whilst alignment is in progress.

DCS: F-15E by RAZBAM - Known Issues

• Bombs dropped in AUTO mode can land long of target for wings level release. It is recommended to do a dive bombing for improved accuracy.
• CBUs can open prematurely, specially if dropped above 1500 ft AGL
• HUD Repeater in MPCD sometimes not visible
• MFD exports not yet implemented
• Volume control for TEWS & TACAN WIP
• WSO HOTAS commands WIP
• AA/AG Gun piper aims high.
• Some items on UFC not synced between front and back cockpit - WIP
• Cockpit Mirrors not symmetrical
• Rear cockpit MFD displays cannot be programmed.
• It is not possible to change the GBUs laser code with the kneeboard.
• Sometimes PACS does not automatically recognize a weapons load. It must be manually entered.
• GUARD is not monitored when selected in the Presets and active mode is Manual Frequency
• Using AG Radar HRM mode can cause a drop in FPS during the image digitalization phase. This depends on the running computer specs.
• Very Rarely, when using AG Radar, DCS will freeze for a second while checking the terrain. This depends on the running computer specs.
• It is recommended to use the AG radar with DCS MT.
• AI wingmen will attack with gun only despite having more relevant ordnance.
• Dumping fuel will cause fuel totalizer to read 0.

DCS World

• New IA mission for Sinai Map: MiG-15bis, F5E, and Su-25T
• MT. Shaded 3D models in ME and Encyclopedia
• ME exits without Save prompt when closing Encyclopedia with a double-click - fixed
• MP. Server. Missions lists are now separated. MP mission launched from ME would be always shown as a single one in list while ordinary mission list accessible from MP menu will not be purged
• Train horn sound fixed
• Cancel button not working in game options/system - fixed
• ME. Egypt. Historical database checked and corrected
• ME. The crew's radio is enabled 
• MANPAD units will not have smoke damaged effect after being hit
• Fixed several crashes in certain situations
• NS430 Persian Gulf crash on zoom out to 200 nm - fixed

DCS: Flaming Cliffs by Eagle Dynamics

• Su-33. Heavy sky mission 20, Immobile Kuznestov makes takeoff impossible - fixed
• Fixed Sinai QS missions
• Fixed radio communication in the IA mission F-15C
• Fixed CTD when leaving Gazelle slot then spawning in a FC3 aircraft

DCS: A-10C II Tank killer by Eagle Dynamics

• ARC-210:Incorrect display of the symbol "," on comm page. -minor: comma will also be filtered out from ARC-210 preset name

DCS: F/A-18C Hornet by Eagle Dynamics

• Fixed: Using SEQ UFC wp delete function causes crash

DCS: Mi-24P Hind by Eagle Dynamics

• Fixed: Searchlight multicrew desync
• Fixed: Petrovich AI switch targets in the loop sometimes
• Fixed: Fuel shut-off valve sound

Campaigns

DCS: F/A-18C Inherent Resolve Campaign by Looking Glass

• Just one mission and a new PDF

DCS: AV-8B Hormuz Freedom Campaign by SorelRo

• Weapons loadout changed as per latest AV-8B update for mission 12 and 7 and briefing text changed for mission 3.

You must know by now there are issues, but I don't know if you're aware that launching the MT version for my account, which pre-purchased the F15E-SE does not show the module ANYWHERE inside the game. The Website shows the order where the module was purchased for the discount price of 56, and the module shows as "BOUGHT" with an "You already own a License for this module" underneath it, but inside the game engine, I cannot find the module anywhere. Neither under installed modules, available modules, NOWHERE. What's going on? Should I re-log in? If that's the case, please consider having your team split up your API calls and separate login from checking for modules. It shouldn't be that hard.

Wait a minute, I tried filing a support case and it says in there that New Modules that have just been released are ONLY in Open Beta? Why not make that clearer to the customer, why do put us through having to dig through this or even having to remember it? I'd be perfectly happy with the same disclaimer inside the module manager in the game engine. Thanks!

Edited June 23, 2023 by einarabelc5

[Art-J]

^ Not wanting to state the obvious, but just to be sure - you're on the latest Open Beta build and you checked in the module manager if the plane is ready for download and install, right?

[einarabelc5]

12 minutes ago, Art-J said:

^ Not wanting to state the obvious, but just to be sure - you're on the latest Open Beta build and you checked in the module manager if the plane is ready for download and install, right?

No, that's what I meant on the last paragraph, of course I'm not in Open beta, that's why I don't see it when I triple checked. But I'm not supposed to know that out of the top of my head and even if I knew it, I could easily forget it. I haven't seen a release since the F-16 came out, and that one is still in "Early Access", I think then I was on Steam Open Beta so I had no clue. It just left a bad taste in my mouth that I had to file a support case to find out the intricacies of the game...that's not normal software customer experience, even if "technically" make sense.

As a software engineer of many years, when I'm the user I want the software to treat me as if I were stupid, to be easy, and only powerful when I wish to think instead of making me work for it and I know for a fact I'm not the only one on the field who thinks the same way, it doesn't give me ANY pride to do the opposite... I troubleshoot enough as it is for a living and don't have the energy or patience to go back into that mode after a long day, even if I can.

Like I said, putting the darn disclaimer in the module manager instead of buried under 4 different clicks in a website stuck somewhere and having the user  guess what category of the support case should it be in order to "prevent" the user for filing a case that has a perfectly logical explanation and requires no real support is NOT good UX, even if from a technical standpoint (and I agree) putting the new modules in open beta is making perfect sense.

With all that said given the track record of DCS, this is like a joke now, since planet Earth in DCS is actually the Twilight Zone or The House of Mirrors...complicated for the sake of it...ah, well, that's enough DCS for today, I'll wait until it goes on release.

Edited June 23, 2023 by einarabelc5

[Tom Kazansky]

37 minutes ago, einarabelc5 said:

Wait a minute, I tried filing a support case and it says in there that New Modules that have just been released are ONLY in Open Beta? Why not make that clearer to the customer, why do put us through having to dig through this or even having to remember it? I'd be perfectly happy with the same disclaimer inside the module manager in the game engine. Thanks!

To be fair, is there any information from ED where they forgot to state that you need the DCS 2.8.6... version?

The reason why there is no disclaimer in the module manager of the stable version is the same reason why you can't find the F-15E in it.

For the future it might help to be aware of the fact that every module comes to open beta first.

[BIGNEWY]

Store page has everything you need to know about which version to use
https://www.digitalcombatsimulator.com/en/shop/modules/f-15e/

DCS: F-15E by RAZBAM

Early access (What is DCS World Early Access?)

Requires DCS World version 2.8.6 or above!


Current version numbers

Latest stable version is 2.8.4.39731

Current openbeta is 2.8.6.41363

[Art-J]

@einarabelc5Wrote my post before you added your last paragraph. Now we know what the issue was.

Well, as a software guy you should understand: new feature added to program -> new program build number. And since Open Beta is by definition the newest build made available to public customer -> it IS always the newest build number at the moment and thus only it can have that new feature.

The only other solution would be to have beta and stable version updated to the same build together (meaning the same bugs and problems in both)... but that would defy the purpose of having the beta in the first place. ED tried it for some time a few years ago, with obvious catastrophic results.

It's all logical - whenever any new content is added to the game, it ALWAYS goes to open beta only as that's the only one with latest build number. So not much to remember, you make it a bigger problem than it really is.

Also, how could your stable version module manager display info about new product (even with relevant disclaimer) if the stable is the older game build and thus it doesn't even "know" there's a separate version  out there?

Granted, questions like this, from inexperienced customers, always pop up on the forum whenever new module is released, I'll give you that. I guess maybe ED could make that folding news-info tab (the one which shows on the left side of the main screen on newsletter Fridays) appear on any other release day as well, with info about module X just being released for open beta. Could be useful for novice DCS users indeed, especially if they made a pre-purchase months ago and don't need to visit the store page. For all the others, though, info about latest open beta number requirement is always displayed on the store page (not sure how it looks on Steam).

[Tom Kazansky]

6 minutes ago, Art-J said:

I guess maybe ED could make that folding news-info tab (the one which shows on the left side of the main screen on newsletter Fridays) appear on any other release day as well, with info about module X just being released for open beta.

This could be helpful

[BIGNEWY]

7 minutes ago, Art-J said:

(not sure how it looks on Steam).

In the info below the main headings

https://store.steampowered.com/app/2316890/DCS_F15E/

ABOUT THIS CONTENT

DCS: F-15E

IMPORTANT! The Open Beta version of DCS World Steam Addition must be used. 

[draconus]

Since we already had earlier version of OB 2.8.6.41066 the info on both E-shop and Steam* would be wrong for anyone that did not update their OB yesterday but still expected to play F-15E.

*Steam updates DCS automatically afaik but it still takes time.

[St4rgun]

The new patch with the F-15E is nice, with the following notes (MT, VR, SP only):

• the automatic exposure control still makes everything outside of the cockpit overexposed which is a pity especially on Sinai which is otherwise a nice desert map. In external view the colors are well defined and the visuals are perfect, but looking from the cockpit it's a washed out mess. I hope this overxposure will be cured really fast (at least turn it off / make it optional at last)
• the occassional visuals' freezing is still there which can last for 4-5 seconds, including blackout while the sound is playing fine. Very disturbing to experience it prior to a touchdown... Fortunatelly it happens really rare, but this was not existent in ST, looks like the game caches SOMETHING.

Dear @BIGNEWY the previous bugs are core related and exist since the introduction of MT. It's really a shame now that we didn't got any usable feedback on those problems.

Is this really so complicated? Is it really impossible for the devs to turn off the auto exposure control or make it optional as long as they're trying to fine tune it? Is this issue really so minimal that no one cares about is? I was really patient for months, but now I'm started to get angry...