Print

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

[kaxII]

yeah i found it, would be good to implement it though.

[SAS~Anto]

When I'm ready. The Bf-109s have been out for a long time, so repacking them all is not a very high priority.

[SAS~Anto]

With the latest SAS Buttons v10.1 on ModAct v4.0, this pack is 100% compatible with 4.11.1m

[mikejr]

Hi Anto,

With the release of ModAct 4.0 I've upgraded my 4.11.1 to it today. It all worked fine when I tested it after the addition of the modact on the clean install of the original 4.11.1.

However, installing your 109 pack (one of my favourites in 4.10) results in a problem which I am unable to solve or even find the cause of - see below:


These are the only mods I have:


As you can see, all I have installed really is your mod; I disabled the 109 cockpit mod thinking that was the problem, anything else is a sound mod which I cannot see as being the issue...  There is nothing in the log.lst or any error reports, and the Windows event viewer isn't much help either...

I know that the maturing of mods to 4.11.1 is really in early days but is there any chance of help, since this post states this mod is compatible? 

Thanks in advance,

Michael.

[BravoFxTrt]

For the Ultimate Pack, You have to have the Cockpit Mod activated. Something else is causing your problem. What does your Log.lst read?

Also try deactivating all other Mods one at a time to see which one is causing problem...

[SAS~Anto]

Yeh a few people have reported 30% crashes in their game and I am not 100% sure of the reason.  Try disabling that sound mod for now and see what happens. Also if you can provide us with the log.lst, that would be handy. Also does it occur on any aircraft in particular?

This pack is slightly out of date but I'm going to wait until JapanCat has done more of his 3D updates before I return to it.

[Mick]

... may be this kind of bug is not specific to your Bf109 pack, Anto, see reply #127 here:

https://www.sas1946.com/main/index.php/topic,27211.msg329454/boardseen.html#new

[ANDYTOTHED]

I have had this problem with modact 4.0. In this case, it is both mods; the cockpits and planes. It doesn't just happen with the 109s, a host of other mods have this problem and I have no idea why. Some of it is just code discrepancy as far as I can tell and it is annoying that the game waits till mission loading to crash.

[mikejr]

Yeh a few people have reported 30% crashes in their game and I am not 100% sure of the reason.  Try disabling that sound mod for now and see what happens. Also if you can provide us with the log.lst, that would be handy. Also does it occur on any aircraft in particular?

This pack is slightly out of date but I'm going to wait until JapanCat has done more of his 3D updates before I return to it.

Hi Anto,

Nope, can't get it to work. Tried changing the order of the 109 mod folders, disabled TrackIR in conf.ini, disabled sound mods. No luck. Every time there is the same crash as seen above. It happens on every 109 I tested, but I have no other aircraft mods so it doesn't occur with any of the stock aircraft.

There is nothing to show from the log.lst file because it is empty and 0kb in size. I'd suggest this isn't fully (if at all) compatible with 4.11.1, which saddens me, because I'd love to use one of my favourite mods from 4.10 in 4.11 with its frankly far better AI.

Guess I'll have to go back to 4.10, and just have 109 sounds in 4.11, and I will wait patiently until the necessary updates are made!

Michael.

[Mick]

... did you try with "instant log" ...?

https://www.sas1946.com/main/index.php/topic,19308.msg207722.html#msg207722

[mikejr]

... did you try with "instant log" ...?

https://www.sas1946.com/main/index.php/topic,19308.msg207722.html#msg207722

No, haven't tried that... will check it out later though. Do you think that perhaps the AutoDiffFM mod might help?

Michael.

[Mick]

... well I have no idea since I don't use 4.11.1, may be this is worth a try, but at least with instant log you should have something in your log.lst file ...