Print

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

[Epervier]

Text by Drewm3i

IL2 4.12 with SAS Mod Activator v5.1 for 4.12m +mods,Revisited NWEurope map retextured, retowned, revillaged by may-bug

... tigers you need to use 4.09 verison, I put the 2 SFS files in the main game folder, then removed the buttons file and the rc. file from the #_UV3 folder in the jsgmemods 4.09+Up2.01 option and placed that #_UV3 folder directly into the #SAS folder, making sure that it is the first folder in the #SAS folder to load. Then I added @sfs MOUNT tigersounds_1.sfs and @sfs MOUNT tigersounds_2.sfs to the rc. file in the STD folder inside the #SAS folder. Make sure you have the HardwareShaders=1 in your conf.ini. I'm using a mostly vanilla version of v.412 with Modact 5.1. And that should do it

[Drewm3i]

So 1) place the two tiger sfs files in your main game folder. Then, 2) download the 4.09 tiger jsgme package and place the UV3 folder inside that package into your #SAS folder. 3) Next delete the buttons and .rc files from inside that UV3 folder. 4) Add @sfs MOUNT tigersounds_1.sfs and @sfs MOUNT tigersounds_2.sfs to your .rc file in the STD folder, but be sure that the two lines you added are at the top of the @sfs MOUNT's. Then you should be good to go.

[flightdok74]

Thanks....that got it.....works great now........ ...... ......you will need the "flyby" delay fix also........

[Mick]

... OK, THX for posting Epervier and Drewm3i, I hope from now on,  many guys will be able to get UV3 in a 4.12 install ... 

Sorry that I can't check this, since I only run a 4.09 version of the game, but if several guys confirm that it also works for them, then I'll add this "fix" to the first page ... 

[Drewm3i]

To get proper flyby sounds you need have a [MOD] section in your conf.ini. In that section you need to set flyby=1. So,
[MOD]
flyby=1
Also make sure you have these in your conf.ini:
[sound]
Attenuation=7
SoundMode=2
SamplingRate=2
NumChannels=4
SoundFlags.hardware=1

[too-cool]

To get proper flyby sounds you need have a [MOD] section in your conf.ini. In that section you need to set flyby=1. So,
[MOD]
flyby=1
Also make sure you have these in your conf.ini:
[sound]
Attenuation=7
SoundMode=2
SamplingRate=2
NumChannels=4
SoundFlags.hardware=1

How do you get the flybys to not loop, ie, play for 10 seconds then repeat? Thanks TC

[Mick]

... UV3 flybys don't loop for me ...  ???

... and once the AC has flown by then it gets away from my point of view until the engine sound fades away so much that I can't hear it, and unless I steer the plane back to where it all started I have to hit F3 again if I want another flyby sequence to be played ... 

You mean that your flybys loop like in stock game ...?  ???

[Mick]

After discussing this point with Epervier it looks like I must have a "special" version of UV3, since Epervier's got the flyby loop too ... 

I remember discussing that aspect with Tiger while beta testing UV3, and the non loop flyby was intentional on his part as it allows you to still have control on your plane while in flyby mode, you can for ex steer your plane towards you and get another flyby effect ...

Am I the only one ...?  ???

[too-cool]

I have in HSFX 6.17 the same as you but in 4.12.2 it now loops, but wasn't there a patch to stop the looping?  TC

[Mick]

... well since I don't have a 4.12 install I have no idea, may be post your log just in case we can spot something ... 

Most of the time DT patches come with changes in the code that could easily explain such "side effects" ... 

After rediscussing the matter with Epervier (4.09+UP2.01) it appears we were in fact saying the same thing differently, and the conclusion is that we have the very same flybys, with no loop at all, unless the plane waypoint steers it back to the camera (either manually if you fly the plane, or "automatically" through the waypoint in the .mis file) ...   

[Drewm3i]

I don't have the flyby loop.

[Mick]

... THX for reporting, Drewm3i ... 

So, too-cool, there could be something wrong with your 4.12.2 UV3 install (or may be a conflict with some other sound mod)...