Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[blackshark]

I have one question ... because i am trying to understand il2 structure and how-to

In the original #_Uv3 folder (for dbw) there are also .rc and gui/buttons ....

But ... why? We already have .rc in STD, so, maybe because we have to mount the tigersound.sfs in the .rc?

And what about buttons ? I ask you that because i copied the last buttons (2013) in STD then i discovered that an older buttons is in UV3

So i have a doubt ... maybe that UV3 really works fine only with the buttons in its folder?

[Epervier]

In the original #_Uv3 folder (for dbw) there are also .rc and gui/buttons ....

But ... why? We already have .rc in STD, so, maybe because we have to mount the tigersound.sfs in the .rc?

Yes.
You must "mount" the two SFS files.
Add the two lines in your .rc ! After the last lines "@sfs MOUNT xxx".

@sfs MOUNT fb_clay01.sfs
@sfs MOUNT fb_clay02.sfs

Attention! Never try to rename the".rc" file!
Copy it to another folder... but never rename it!

And what about buttons ? I ask you that because i copied the last buttons (2013) in STD then i discovered that an older buttons is in UV3

So i have a doubt ... maybe that UV3 really works fine only with the buttons in its folder?

To benefit from the sounds and especially from the flyby specific to UV3 (it is the same for UV2) you need an adapted button.
SoundName"/"PropName"/"StartStopName" calls are different in EMD!

That's why I provide in my " bricolages " the different external FMs for the SAS/UV2/UV3 buttons!
And that I update the three types of buttons.
https://www.sas1946.com/main/index.php/topic,23404.0.html
But since no one else did the same for the 410 buttons, I'm afraid you're having problems...

[blackshark]

Thank you very much for your answer.

So I suppose it would be better to maintain the uv3 buttons (2012) and do not upgrade them to the last available version (2013), is it correct?
 

[bomberkiller]

bs,

If you mean my DBW, leave it as it is!

Example "# _Me262Pack_Bk":

This pack with everything to do with Me-262 is only there twice, yours and mine! If you change even a small thing here #DBW is destroyed.

Regards, Gerhard

[blackshark]

Hi Gerhard

no I will not touch your config.  For me it's like a "black box", I enjoy it "as is", and I enjoy it for sure 

Meanwhile I like to learn how-to in IL2 with my smaller config and the more I learn to more I like it