Print

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

[PO_MAK_249RIP]

Hi Cirx - can we expect similar issues with UltraPack 3.0?? Or is this problem (which thankfully I dont have) isolated to ModAct installs ?

[cheesehawk]

Ok, my installations work fine, but I'm having a graphical issue.  Playing on a private server for a squad vs squad campaign, 4.101 mods allowed, I'm running the SAS Modact installation with ecran wide and 6 DOF as the only mods activated, my plane trails smoke for everyone using a stock 4.101 installation.  Nothing is physically wrong with my plane, but several people (both opponents and friendlies) reported my plane was smoking heavily from the start.  Even weirder, they think it looks like I'm smoking from the wings, like a black, thick fuel leak.  No damage was taken by my plane in 2 starts, but I was smoking each time.

[SAS~Storebror]

Smoke trails usually point to a buttons issue.
There are offline and online buttons available. In case of mismatch, onliners will see you smoking i.e. when you're using offline buttons and open the canopy.

Should make me wonder if that's related to the Modact itself in any way.

Best regards - Mike

[Nicholaiovitch]

Ok, my installations work fine, but I'm having a graphical issue.  Playing on a private server for a squad vs squad campaign, 4.101 mods allowed, I'm running the SAS Modact installation with ecran wide and 6 DOF as the only mods activated, my plane trails smoke for everyone using a stock 4.101 installation.  Nothing is physically wrong with my plane, but several people (both opponents and friendlies) reported my plane was smoking heavily from the start.  Even weirder, they think it looks like I'm smoking from the wings, like a black, thick fuel leak.  No damage was taken by my plane in 2 starts, but I was smoking each time.

We had a Bf110 on Sunday night smoking on our server. Turns out the chap did not load "Stock".exe. Since it is a private link up without server software, there is no CRT=2 check and it is possible to join without realising that the host is running "stock" 4.01.1.

It is a matter of finding out whether or not mods are in use. If the server is running "Stock" 4.01.1 as ours on a Sunday (Mods on Thursdays) you will get smoke from some a/c if you run the SAS.exe as it will load the SAS buttons.

Perhaps you server was running 4.01.1 "Stock"?

Nicholaiovitch

[cheesehawk]

Yes, it was, but was told that mods were allowed, which I assumed meant SAS Modact would be fine.

[Nicholaiovitch]

Yes, it was, but was told that mods were allowed, which I assumed meant SAS Modact would be fine.

No problem old chap....just to clarify your first post.......it is not a problem with the SAS activator ....it is a well documented problem of trying to fly online with a loaded "Offline" SAS buttons file on a vanilla server that causes a smoke trail on some a/c.

Just use the wonderful new selector in SAS 3.2 before your game loads and hit "Settings" before the time out, then hit "Stock Game" and save. Now you will be most welcome on all 4.10.1 servers with no smoke trail to give yourself away to the enemy.

Good luck,

Nicholaiovitch

[cartfather229]

How do I make a new drive for the game, opposed to program files?

[SAS~CirX]

I buy a second hardrive, put it in you PC, copy IL2 to it, et viola!

if you just have one hardrive, open it ( probably called C:) and make a new folder at it's root. call it whatever you like. Then cut and  past, or copy and paste, or drag, your IL2 instllation(s) folder into that folder.

I bought actualy today a new seagate 1TG drive, popped it into my PC, used Easus Partition thingy to partition it into 3 drives, and copied stuff over to it today. nice! (my previous 2nd drive was a measely 160GB.) I loaded all my IL2s onto one partition, and played some missions without a hitch.

Although I have to add, on my PC, IL2 is virtually crashproof, because I have a highly customised proprietary liveware application that detects any issues and sorts them out automatically.

[cartfather229]

So... just drag/ whatever into something other than C:? Doesn't seem so hard, I'll get to work on that! What do I do with my IL-2 installation already in my program files folder, get rid of it?

[SAS~CirX]

You can leave it there and ignore it forever more.

[cartfather229]

Thanks man, I'll do that, then put on 3.02

[cartfather229]

Even with 3.0 in my new folder, it doesn't work, crashes on intro... and for stock IL2, airplane's bottom sides show up in blue, what the heck!