Print

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

[fabo28]

Froggy,

Don't know if you solved the 'missing' Tiffies issue you reported earlier, but I found a second instance of Crazyflak's Typhoons and Tempests in Monty 17, they were already installed in on of the earlier packs..

I put a '-' in front of the second instance and the Typhoons re-appeared.


pied

Salut pied!

I actually had no issues with the Typhoons/Tempest, I think it was Fabo28. Mine are accounted for! 

My bug is the Lancaster not loading (it's present in the selection, but doesn't load or cannot be viewed in the FMB object screen/QMB aircraft customization). I still need to check a few things out though...

Thank you Pied and Froggy, applied what Pied said (I deactivated packs from 18 to 16, put minus sign in front of Crazyflak`Thyphoons in Monty pack 16 (not 17) reloaded again et voila, my Thyphoons are back!)
Just in case someone else is having same problem this works,

[SAS~Monty27]

Just to be clear.  It is NOT 'a second instance of Crazyflak's Typhoons and Tempests in Monty 17' - The individual plane folder sizes are clearly larger and far fewer.  This is an update which adds the Typhoon Mk1a.  They are all there.  The confusion in several recent posts over folder names is often down to a failure to understand the structure of these packs.

For the record, folder names from modders have sometimes been changed for compatibility and load order functions within TFM.  For the list of what should be there, check the front of post.  Seeing a folder twice does not necessarily indicate a repeat or error.  Likewise, not seeing an expected folder name also does not necessarily mean a mod isn't there, that's not how it works.

It appears the most people have 'no issues with the Typhoons/Tempest' - so something else is going on.

If it works for you - fine.  But I can't post a fix or suggestion if I don't see a problem or have any hard data.

[Sonny Tucson]

Hi Sirrover , Hi Monty

Just had a fresh download of MONTY'S 15 and installed it . I compared it with the one I used and they had the same size and... same result , crash at 70%.

Please is there another way to get a logfile , this stuff is driving me mad. I am trying hard since 3 days to get it to work . Look at my earlier posts , I did everything by the book and it looks like I am the sole to have problems.

Sonny.

[352nd_Hoss]

Hi Sirrover , Hi Monty

Just had a fresh download of MONTY'S 15 and installed it . I compared it with the one I used and they had the same size and... same result , crash at 70%.

Please is there another way to get a logfile , this stuff is driving me mad. I am trying hard since 3 days to get it to work . Look at my earlier posts , I did everything by the book and it looks like I am the sole to have problems.

Sonny.

Why don't you ask Simon to send you his air.ini file from Monty 15 and compare it to yours, that's where the problem lies, and the air.ini is easy as hell to email.  Get WinMerg program and compare the two files, put in your's what Simon has in his and you should be good to go. 

[csvousden]

I have to admit that I also had a problem with the typhoons and the Junkers 87s after adding the 15th pack.  Also my L-139 had a strange phenomenon with the gun.  I can live without the Typhoon MkIa if that is the problem. 

I have not reloaded 15 or up just yet.

CV

[Sonny Tucson]

SOLVED 


Hi Sirrover , Monty and AG-51

I finally got my packs 15-16-17 and 18 installed and running at 03.30AM .

Something very weird has happened.
As you know my game was running fine till enabling PACK 15.
The problem arised when enabling Pack 15. I always got a 70% crash. Not having a logfile I couldn't spot the problem. Whatever I could do ( redownload the pack 15 etc etc... ) the crash was still there. All this time I didn't have a look at my root directory but well in my ROOT/#DBW directory to check all the mods installing themselves.


The problem was that my GME ( for a reason that I still ignore ) had placed  #DBW_MONTY-14 in my root directory without transferring  his content in my ROOT/#DBW folder and without inducing a 70% crash at the game start !.Moreover in my GME #DBW_MONTY-14 was well on the right side (enabled).
I suppose that the game was in fact running the DBW_MONTY-13 !
As soon as I noticed that I took the content of #DBW_MONTY-14 and put it in my ROOT/#DBW folder allowing overwriting. The sole folder that I left in my root DBW_MONTY-14 was the "documentation" cause I didn't know where to put it !.
Then I enabled MONTY-15 and my game finally started !-
After that I proceeded to PACKS 16-17 and 18 checking if GME had not placed these packs again in my Root folder.
I had no problem with these installs.
My game is now running.
In my excitement I forgot to disable PAL COCKPIT SOUNDS from Pack 17 !
In my GME on the Enable list , MONTY 14 is still in black ( not greyed ).
Maybe because of the documentation that was left in the pack 14 folder ?

Thanks for your help.

I still do not know how such a thing could have  happened !.

Sony 

[SAS~Monty27]

SOLVED 


Hi Sirrover , Monty and AG-51

I finally got my packs 15-16-17 and 18 installed and running at 03.30AM .

Something very weird has happened.
As you know my game was running fine till enabling PACK 15.
The problem arised when enabling Pack 15. I always got a 70% crash. Not having a logfile I couldn't spot the problem. Whatever I could do ( redownload the pack 15 etc etc... ) the crash was still there. All this time I didn't have a look at my root directory but well in my ROOT/#DBW directory to check all the mods installing themselves.


The problem was that my GME ( for a reason that I still ignore ) had placed  #DBW_MONTY-14 in my root directory without transferring  his content in my ROOT/#DBW folder and without inducing a 70% crash at the game start !.Moreover in my GME #DBW_MONTY-14 was well on the right side (enabled).
I suppose that the game was in fact running the DBW_MONTY-13 !
As soon as I noticed that I took the content of #DBW_MONTY-14 and put it in my ROOT/#DBW folder allowing overwriting. The sole folder that I left in my root DBW_MONTY-14 was the "documentation" cause I didn't know where to put it !.
Then I enabled MONTY-15 and my game finally started !-
After that I proceeded to PACKS 16-17 and 18 checking if GME had not placed these packs again in my Root folder.
I had no problem with these installs.
My game is now running.
In my excitement I forgot to disable PAL COCKPIT SOUNDS from Pack 17 !
In my GME on the Enable list , MONTY 14 is still in black ( not greyed ).
Maybe because of the documentation that was left in the pack 14 folder ?

Thanks for your help.

I still do not know how such a thing could have  happened !.

Sony 

Well bugger me!  The JSGME INI file controls where it goes, that must have been altered at some point.  Never mind, good result.

Having used JSGME to build and test TFM it seems that TotalModder is more successful in terms of speed and profile switching.  Even better though I prefer SAS~BravoFxTrt's solution, and Hoss does a similar thing, just get a clean #DBW folder and throw it all in there yourself, in order!  The Tiger33 and Claymore sfs files go in the main install directory (the only exception) and there it is!

Do this with Monty-19 and Monty-20, the final packs have some too nice mods we can't live without...

Do delete 00_PAL cockpit Sounds from you current #DBW and Monty-17 then you won't have to mess around with anything else.

One more thing, it was rough on some of you, piece of cake for most, but a LOT of people are now a hell of lot more modded than before TFM, however you got there!

Simon(Monty27)

[Gerson]

Hi Monty
I could solve my problems and now the game is loading succesfully.
I changed to TotalModder and TFM loads fine and works in just a few seconds
I encourage everyone to give it a try.
You just have to copy some sfs files into the roots game directory and everything runs fine.
All the Best
Gerson

[nuke11]

Just to be clear.  It is NOT 'a second instance of Crazyflak's Typhoons and Tempests in Monty 17' - The individual plane folder sizes are clearly larger and far fewer.  This is an update which adds the Typhoon Mk1a.  They are all there.  The confusion in several recent posts over folder names is often down to a failure to understand the structure of these packs.

For the record, folder names from modders have sometimes been changed for compatibility and load order functions within TFM.  For the list of what should be there, check the front of post.  Seeing a folder twice does not necessarily indicate a repeat or error.  Likewise, not seeing an expected folder name also does not necessarily mean a mod isn't there, that's not how it works.

It appears the most people have 'no issues with the Typhoons/Tempest' - so something else is going on.

If it works for you - fine.  But I can't post a fix or suggestion if I don't see a problem or have any hard data.

What pack is the Typhoon Mk1a added from? As I don't have a Typhoon 1a in my install and I have upto Monty18 installed and working.

Thank you.

[sirrover]

To support Mr. Gerson's appeal to use TotalModder I'd like to share one secret weapon that magnificent Mr. chupag72 taught me when I was just an egg.
Okay, here's the procedure before you start using TotalModder:
1. Go to your jsgmemods folder and create a folder called smth like (not relevant) DBW_Root or smth like that
2. Find the following files in Monty packs and copy (or cut and paste) them to this folder



Contents of 0_BACKUP folder



Contents of Paintschemes/Skins folder



Don't ask me why - I only know that it works perfectly.

3. Activate this folder in your JSGME activator.

After this is done you can safely proceed with classic TotalModder installation described in details in corresponding threads. And even somewhere here, I guess.

After this procedure you can forget about JSGME and neverending copying and deactivating of huge modpacks. Just one click and all 18 packs can be activated in 5 seconds.

Thanks to Pablo, Monty and chupag72 (who showed me how the stuff works + some other tricks  )

[Gerson]

Hi sirrover, this procedure is necessary because Total Modder dont copy folders in the games root, and this is where those files need to be copied.
So you have to copy these files with the jsgme, and AFTER that proceed with the activation of the packs through Total Modder.
All the Best
Gerson

[Camman]

As a complete noob myself I would say TotalMODder is the way to go, you dont have to overwrite anything at all, it loads super fast, your up and running super fast, and it makes activating and deactivating pmods a snap. Troubleshooting is much much easier with totalMODder, it keeps your install small, you can have multiple instances, it really is just plain awesome.

I also load my monty campaigns through jsgme as well just in case lol.