DCS World 1.2.12 Discussion

[Skitter]

Wow! This is update will bring a serious potential to the combined arms. Can't wait!! Thanks ED

[Lib]

Did they fix the custom radio bug in multiplayer ? or do clients have still no way to do a homing in huey ?

[Rangi]

Bit OT but anyway, has it been announced which WW2 fighter is coming after the 109?

[SyntaxError]

Bit OT but anyway, has it been announced which WW2 fighter is coming after the 109?

Not entirely sure but I'm going to say the Spitfire IX?

[ThorBrasil]

ED you can correct this error? When the anti-collision light is turned on. It cuts in the cockpit. And the outside view he is right. Just inside the cockpit que this happens. In all aircraft and all types of lights. It's like a limitation Placed on the cockpit. The light has to get out from under the aircraft. And not just in front. Looking marking in blue. She should have the Anti-collision light from under the aircraft.

Edited December 3, 2014 by ThorBrasil

[Cibit]

Can anyone comment on the HOTAS profiles that have been added?

[Boris]

Not entirely sure but I'm going to say the Spitfire IX?

 

Yes, the Spitfire was tentatively slated for December, but we've only just got the Bf-109, which was initially gauged for October.

 

I guess by that logic we may see the Spitfire in February.

[BBQ]

The actual dropdown menu to select custom textures seems to be hidden. I browsed the directory structure though, and found this readme:

 

--/N/ v.3 Nov 2014.

------ CUSTOMIZATION DISCLAIMER ---------

Leatherneck Simulations holds no responsibility for your customization, cockpit liveries errors, general MiG-21 loading errors or any other error or damage that might happen as a result of inappropriate DCS MiG-21BiS customization.

Customization of cockpit livery or other DCS: MiG-21BIS files is solely users responsibility.

-----------------------------------------



1. Folder default content


By default, this folder contains only

description.lua

file, which will enable default (original) cockpit livery to behave as a custom livery.



2. Enabling custom cockpit livery

To enable custom cockpit livery, you can either make one by copying and editing one of original Leatherneck's liveries (e.g. MiG-21BIS\Liveries\Mig-21_CP\english) or you can download already created livery from known and trusted DCS community sources (like Chinese or Finnish cockpit livery).

Your livery files along with description.lua should be placed in this folder.

Make sure you know what you are doing before attempting customization.



3. Credits

Idea for custom cockpit livery option by Xueqian Zhao (AKA uboats).

 

 

didn't anyone notice the switchable cockpit texture by drop-down menu for mig-21bis? Glad that LN has done this.

[Aginor]

You just gotta love the Leatherneck guys!

[Nate--IRL--]

ED you can correct this error? When the anti-collision light is turned on. It cuts in the cockpit. And the outside view he is right. Just inside the cockpit que this happens. In all aircraft and all types of lights. It's like a limitation Placed on the cockpit. The light has to get out from under the aircraft. And not just in front. Looking marking in blue. She should have the Anti-collision light from under the aircraft.

 

This is actually a product of the way cockpits in DCS are drawn - it has been flagged for years, present since Lock On, and will take a major reworking of Cockpit rendering technique to fix. I personally hate it too.

 

Nate

[ThorBrasil]

This is actually a product of the way cockpits in DCS are drawn - it has been flagged for years, present since Lock On, and will take a major reworking of Cockpit rendering technique to fix. I personally hate it too.

 

Nate

 

This reshaping will take to arrive? Thanks! +1

[uboats]

The actual dropdown menu to select custom textures seems to be hidden. I browsed the directory structure though, and found this readme:

 

--/N/ v.3 Nov 2014.

------ CUSTOMIZATION DISCLAIMER ---------

Leatherneck Simulations holds no responsibility for your customization, cockpit liveries errors, general MiG-21 loading errors or any other error or damage that might happen as a result of inappropriate DCS MiG-21BiS customization.

Customization of cockpit livery or other DCS: MiG-21BIS files is solely users responsibility.

-----------------------------------------



1. Folder default content


By default, this folder contains only

description.lua

file, which will enable default (original) cockpit livery to behave as a custom livery.



2. Enabling custom cockpit livery

To enable custom cockpit livery, you can either make one by copying and editing one of original Leatherneck's liveries (e.g. MiG-21BIS\Liveries\Mig-21_CP\english) or you can download already created livery from known and trusted DCS community sources (like Chinese or Finnish cockpit livery).

Your livery files along with description.lua should be placed in this folder.

Make sure you know what you are doing before attempting customization.



3. Credits

Idea for custom cockpit livery option by Xueqian Zhao (AKA uboats).

 

I believe it is not hidden, actually, I looked at the script, the list is not there but just chechbox instead.

[spyro23]

New flares itself are looking really good. On the other hand, smoke trails they now produce is a big step backward IMO. It is no longer "shattered" for a lack of better world (like flare is no longer rotating in the air). Moreover smoke trail seems to dissipate too quickly.

 

[marluk]

My apology if I miss something mentioned before but I have one question. I think that I had latest DCS World update installed. When I saw that new update is announced, I run DCS World update for every case. Not beta.

 

Anyhow, I expected, nothing will happen since I didn't run DCS World Beta update, but the update download has started, and it is huge! It has about 3700 MB !?

 

What's going on? Did I miss something?

[Jumbik]

My apology if I miss something mentioned before but I have one question. I think that I had latest DCS World update installed. When I saw that new update is announced, I run DCS World update for every case. Not beta.

 

Anyhow, I expected, nothing will happen since I didn't run DCS World Beta update, but the update download has started, and it is huge! It has about 3700 MB !?

 

What's going on? Did I miss something?

 

 

Patch was released but official info is yet to be published.

[marluk]

Patch was released but official info is yet to be published.

 

Hm. It is really short beta period then. :)

Edited December 3, 2014 by marluk

[SkateZilla]

Patch was released but official info is yet to be published.

 

Newsletter will likely announce the 1.2.12 release and BF-109 Beta.

[Gate-5]

Newsletter will likely announce the 1.2.12 release and BF-109 Beta.

 

Indeed, I just updated my non-beta version to 1.2.12.34915.571 and was abble to install the BF109 module... :thumbup:

[uboats]

Newsletter will likely announce the 1.2.12 release and BF-109 Beta.

 

nothing about 2.0?

[Rikus]

The shortest beta, 1 day only :P

[SkateZilla]

nothing about 2.0?

 

I was refering to the lack of an announcement that 1.2.12 was releases on stable.

*I do not know the contents of the newletters.

[NineLine]

The shortest beta, 1 day only :P

 

109 is still in Beta

[Fri13]

Bummer the Su-27 trim hasn't been fixed yet. This plane is close to unflyable IMHO. Full trim nose down and I still have to push my stick forward even further to stay level. MS FFB2 with FFB activated, of course, every axis totally linear. Didn't test without FFB yet, but I highly suspect my problem is linked to the FFB trim mechanics somehow as I don't see others complain :D

 

That put aside (as well as the MiG-21 double trim), the changelog looks great, quite something happened, which is always good :)

G940 FFB doesn't have a problem with a trim. Nicely the trimming moves new center where wanted. Need to test it more tomorrow as didn't push it to limits at all.

[uboats]

[xaoslaad]

Static Object MANPADS on the map ( Stinger or SA-18 ) cause 1.2.12 to crash... if your maps are crashing and you have any of these they'll need removal :/

 

I had some on a practice range type map.