FS2004 Kodiak Build 2.0 is now released

Hey LouP,

Embarrassingly enough, I didnt have the effects file for the plane in the original installer. Its now in the new one. (So we can rule that out).

Please request a new download if you purchased through Payloadz, and if you have the Flight1 version, redownload the installer and reinstall it using your key. This will have the effects file along with a ton of extra's done to the configs, gauges, and FSX Models.

When you said that the PFD screen was the one hanging up the system in frame rates (still shows up, but bringing down frames) it occurred to me that the mini popup GPS windows in the bottom left corner of the PFD screen might be 'rendering' at full capacity even when its not being shown, which would be the same as running two different GPS systems in FS. So we (Dwight, the gauge Meistro) recoded the mini map to turn off when not being shown. I am hoping this will solve the PFD issue.

By the way, there is a small issue that crept in with the gauges. Lightmaps placed into the AP and Audio Panel are mis-aligned with the models lightmap. I should have an update for that ready soon. Trying to figure out which route to take on that.


Bill
 
Heads up for all Kodiak pilots.

Update 2.2 is now out. This repaired some issues with the last update that crept into the batch. (Experimental self illuminating gauges). Also some tunes to textures were done, gauge updates to the screens, tidbits here and there.


Note, if you have Flight1 keys, and they no longer work, simply go to the Flight1 website here;
https://www.flight1.com/view.asp?page=keyrequest
and request a new key or reactivating your key.

For people that have version 1 from years ago, email me and I will create the newest key for Build 2.2. My email is william 'at' lionheartcreations 'dot' com. I will need your full name, and your purchase number. If you no longer have your purchase order, go to Service at Flight1.com and look up your order numbers, find the Kodiak, and copy/paste that to me.


Bill
 
Hi Bill, I kept the 14 flights from ver1. Just wondering why you don't include them anymore. Is there now a problem with them?
 
Hey Rich,

With FSX and its complexities, so busy with learning aircraft creation in FSX and not enough time to learn scenery design in 'FSX' Gmax as well, I decided to not have the scenery in FSX. I was then faced with a huge issue with sales if I advertised the scenery with the plane as FSX people would want it. So I decided to basically cancel the Villages and Missions flights of Bolivia. I still include the scenery in the FS2004 version, but not in the FSX version. The flights are no longer there either.


Making scenery used to be quite easy and fun. But now, you deal with everyones versions of land mesh, so the airstrips and all wind up underground in vertical cuts in the Earth, or on towering colums. It became a total catastrophe with the Kodiak. Everyone was complaining because I didnt have various versions for their land meshes.

Operation Valkyrie with 9 airfields (or more) was even worse.. Oh man.... eeks..


That is why. :kilroy:


If everyone had the same land mesh, scenery hills were the same in FSX as in FS9, and scenery making wasnt so different, the Bolivian villages would be in there.



Bill
 
Boy, howdy !! Your right!

Had the missions working and then messed it up when I installed a new Mesh from Genesis. It was imposssibe even to take off as the scenery was UNDERGROUND!! I had to uninstall the South America DVD and your scenery works very well now.

Ed
 
Hey Ed,

Yep.. Scenery will just freak out if there are airfields and you install new mesh.

I installed Mesh in SoCal and it messed up all of my airports in Mega Scenery SoCal. Everything was either in pits or on hills that looked like pyramids.. arrgh..



Bill
 
Bill, I seem to keep getting an 'out of memory' error whenever I choose the Kodiak and create a flight; It doesn't seem to happen with any other addons...Im troubleshooting now but do you have any advice?
 
Here is the error file:

Problem signature:
Problem Event Name: APPCRASH
Application Name: fs9.exe
Application Version: 9.1.0.40901
Application Timestamp: 4135a208
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a7a6
Exception Code: c0000005
Exception Offset: 000681cb
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: f789
Additional Information 2: 71c17f8b599ee1bbc41cd8f706c95bc4
Additional Information 3: e2b2
Additional Information 4: 8f8e949c797018c1336da002fe2af554
 
are you using vista by chance?....once in awhle...i can be using FS9 and things going fie and then i open fs9 and select a plane at it tells me i dont have enough memory
 
Yes Tom, I have Vista 32...but after some testing I'm relatively certian that it isn't the Kodiak now; I may have issues elsewhere...so i am troubleshooting. I will let you guys know what I come up with.
 
Hey Felix,

That crash message says its a DDL if I am correct. Maybe run a Google search on it and see what you can find out on it. You might be able to disable it or run without it. But please find out first. It could be a seriously required system file.


Bill
 
Thanks for the advice, Bill. I think it is a 'windows kernel dll' and is part of the win32 files...don't want to mess with it; Also threw a 'g3d.dll' file CTD as well, which is something completely different. It seems as though something threw my computer for a bit of a loop. I will keep hunting....
 
Felixthreeone said:
Thanks for the advice, Bill. I think it is a 'windows kernel dll' and is part of the win32 files...don't want to mess with it; Also threw a 'g3d.dll' file CTD as well, which is something completely different. It seems as though something threw my computer for a bit of a loop. I will keep hunting....
Click to expand...


Hey Felix,


Roger that.

One thing you could try is disabling the Hobbs meter/timer and see if that does it. Its the only high tech thing in the panel and records flight time to a file in the FSX / FS2004 files folders. That is the only thing I can think of that 'might' trigger a crash in a system. (especially with vista). Too disable it, simply put two slash marks in fromt of the gauge // in both points; VC panel and at the main panel.


Bill
 
Ok Bill thanks for the info...I am running some diagnostics on the registry, and will be re-installing the whole Kodiak V2; I will post the results shortly.
 
Ok so what I have turned up so far seems to indicate that the problem (whatever it is) is only related to version 2.2; I had an instant crash with 2.2...reverted back to 2.01 and no crash. That is all I have so far...
 
ok i take that back....reloaded FS and whammo..CTD when selecting the Kodiak? I am stumped once again.

.....BTW Bill the Hobbs trick didn't do it....
 
I have the same CTD's. XP, IE6 sp2. Have the ctd's with Kodiak version 2.0, 2.1, and 2.2. Remedy is always stop the call of the PFD in the 2D panel.

The error is always the same:
AppName: fs9.exe AppVer: 9.1.0.40901 ModName: ntdll.dll
ModVer: 5.1.2600.2180 Offset: 000122ba

I've researched at least 50 sites pertaining to the system32 file, ntdll.dll. A small number of the posts are FS9 users. To this point there seems to be no concrete "one fix does it all" answer. Those that have had success, report something different that straightened it out.

Usually if the ntdll.dll file is named it is either corrupt, bad drivers, or a software issue. I have replaced the dll with two different versions. No help. Most of my software is disabled or removed. Something within FS9 or the Kodiak is making a bad call to the ntdll.dll file...at least that is what I've surmised from what I've read. Since fs9.exe and the ntdll.dll file are named, there, seems to be the place to start.

That's what I have so far. I fly the Kodiak without the PFD in the 2D panel.
 
You must log in or register to reply here.
Back
Top