This is a re-package of CCMs Twin Otter Mods, which doesn't include any original source files.
The script file included will create new folders and files containing CCMs Twin Otter Mods.
Required files:
The jojodiff file creator, available from here: http://jojodiff.sourceforge.net/
When you've extracted the jdiff085.7z files, open the win folder and copy the jdiff.exe file into your Windows\System32 folder.
Installation:
Note: Because of the way this mod works, it will only work for version 1.0.4 of the Aerosoft Twin Otter. Attempts to install with older versions will most likely fail.
This package contains a folder named CCMs Twin Otter Mods_1.0.5.0_diffs_Qbgky, and a Deploy_CCM_Twotter_diffs_v2.ps1 script file which will create the mod files for you.
Having installed the jdiff.exe into your Windows\System32 folder, simply right-click on the Deploy_CCM_Twotter_diffs_v2.ps1 file and select Run with Powershell from the menu.
A security warning window will pop up, click the Open button to launch the Powershell script.
A Browse For Folder window pops up, navigate to the CCMs Twin Otter Mods_1.0.5.0_diffs_Qbgky folder and click OK.
Another Browse For Folder window pops up, navigate to your Community\aerosoft-aircraft-twin-otter folder and click OK.
The script will run and the Powershell window will close down.
Open the CCMs Twin Otter Mods_1.0.5.0_diffs_Qbgky folder and the modded files are now ready to be copied and pasted into your Community folder:
z-twin-otter-beltssmoking-mod
z-twin-otter-flightmodel-mod
z-twin-otter-HSI-mod
z-twin-otter-sound-mod
The modded files are inside each of these folders. You can select any or all of the mods as you require, they work independently of each other.
Acknowledgements: Thanks to both CCM for the original mod, and for MSFS forum member GBTAW for testing the mod, and providing the text above.
Got through some flights. New problems with climb and cruise performance. It is also impossible to climb 1000fpm with 45 trq, 105knots, at 75% prop rpm now. Cruise is also another problem with losing up to 20knots ias during cruise unless one wants to overheat the T5s.
I believe the original Modder(Capt Moustache) has to amend the mod to suite v1.0.5 flight model changes.
2 years ago
Given what happened between them and Aerosoft that is probably unlikely to happen.
If it performs as you expect with the un-modded 1.0.5.0 we'd have to look at what changed between 1.0.4.0, 1.0.5.0, and what the mod changed, presumably in the flight model file.
2 years ago
Hobanagerik
chinjh
What happened to the original mod of this on this site?
He also had a great flightmodel mod for the Kodiak... seems to be gone as well...
What happenend?
2 years ago
It was hit by a copyright strike. The mod can still be used, you just need to use the Powershell script here to re-create it.
2 years ago
Hobanagerik
THEOLI4D
I have downloaded the file but don't see these files
CCMs Twin Otter Mods_QqCRx_diffs, and a Deploy_CCM_Twotter_diffs_v2.ps1
In fact, there is no difference from before this work around.
I don't understand computers that well....just like flying...need help!
These work arounds are too difficult for someone who knows nothing about computers...shame on aerosoft!!!!
2 years ago
I've reuploaded the file to include the script. I have also updated the description to reference the slightly new folder name that includes which version of the Twin Otter it is for.
2 years ago
Hobanagerik
twnotter
Does this require the TSS sound files?
2 years ago
No. The mod replaces the sounds with those from the King Air 350. Personally I don't use that mod, and I use the one you mention instead.
2 years ago
Hobanagerik
caribstar
I have followed instructions to the letter, and transferred the files to the community Twin otter Folder, but there appears to be no difference to the original files, certainly there is no difference in the twin otter sound.
2 years ago
The original files don't get touched at all. The only files that get changed are the ones in the mod itself. If you look at the ZIP file it will have 55 JDF files. The script uses the Twin Otter originals, plus these JDF files to re-create the original modded files, and then it deletes the JDF files. You won't see any change to the Twin Otter, and the reconstrucuted mod must be installed in the Community folder like any other.
2 years ago
Hobanagerik
DIGGERFAY
Twin otters now does not appear at MSFS after runing the powershell and moving the mod files into community. Does this mod script work for Steam MSFS? Aerosoft twin otter file directory seems to be within Aerosoft One while i have the msfs and its community folder on a separate path both within the steamapp directory on drive D.
Seems like i have reinstall the otter via aerosoft one for now. Also any difference from the latest CCM mods that was removed? Feels like i should use back that mod for now.
2 years ago
That's very strange. I can't see how that is possible as it doesn't make any changes to the Twin Otter folder itself. All it does is manipulate the files in the extracted ZIP file that contains the modified mod, where all its original files have been replaced with JDF files.
Even if you selected the folders in the wrong order, such as choosing the Twin Otter folder first, then the mod, it shouldn't do anything as it won't find any JDF files in the Twin Otter folder.
I don't think it being a Steam release should make any difference, though I haven't tried it as I don't own the Steam version. The relative paths from SimObjects should be identical as far as I know.
2 years ago
Hobanagerik
chinjh
My review is not a critique of the actual or he original mod, as the author did outstanding work in setting this up, but of the general approach taken how this mod is applied.
I understand this is caused by the random copyright claims made by Aerosoft, but I sincerely hope this doesn't set a precedent. I have no problem working with diffs in general, as it's part of my professional work. But I always really liked the very straightforward approach MSFS had to adding and removing mods.
I don't look forward to my first mod patches failing and me going on this goose chase trying to find out: "Does my source not match? Is the patch faulty? Did I do something wrong when I applied this patch?"
Personally, I'd rather have Aerosoft (and myself, as I own it) be stuck with a partially broken plane that they apparently don't want the community's help in fixing instead of making modding complicated for everyone because of a single bad actor.
2 years ago
crotchetycoder
Thanks for the workaround!
2 years ago
wcs33