The download hangar is currently disabled. We're doing our best to bring it back as soon as possible.
Luke AFB package by MAIW
- petebramley
- MAIW Developer
- Posts: 1529
- Joined: 17 Jun 2007, 16:05
- Version: P3D
- Location: EGBG
Have just tried as suggested and the problem disappeared. will now re-install the custom scenery without textures and see what happensFirebird wrote:OK well it seems that we may have an issue here.
So I guess that we need to narrow down the cause. Can the guys that have the problem disable the Luke scenery, but please make sure that the necessary afcad (MAIW_AF2_KLUF_CUSTOM.bgl) is copied to an active directory and then check to see if the same problem occurs at Luke.
The purpose of this is to try and narrow down the cause to the scenery or eliminate it as the cause.
Regards
pete
Can you confirm this, as somebody else has said that with the scenery installed but no textures there is no problem.bismarck wrote:Reinstalled scenery without texture.Problem still there.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Steve, I confirm. I didn't wait till FS9 crash, but after 20-25 minutes, memory in use passed from 580Mb to 950Mb and was still increasing.Firebird wrote:Can you confirm this, as somebody else has said that with the scenery installed but no textures there is no problem.bismarck wrote:Reinstalled scenery without texture.Problem still there.
It is possible that without texture, memory usage is less than when they are installed, so the crash needs more time....just a thought.
BTW, this evening I'll try it again.
Giorgio
- petebramley
- MAIW Developer
- Posts: 1529
- Joined: 17 Jun 2007, 16:05
- Version: P3D
- Location: EGBG
Steve, I confirm. I didn't wait till FS9 crash, but after 20-25 minutes, memory in use passed from 580Mb to 950Mb and was still increasing.bismarck wrote:Firebird wrote:Can you confirm this, as somebody else has said that with the scenery installed but no textures there is no problem.bismarck wrote:Reinstalled scenery without texture.Problem still there.
It is possible that without texture, memory usage is less than when they are installed, so the crash needs more time....just a thought.
BTW, this evening I'll try it again.
Re-checked this evening and as Bismarck says the problem is still there but at a much slower rate (sorry was too quick for my own good)
am now gonna reload Luke from scratch but with the landclass.bgl removed as suggested by Giorgio & see what happens. report back later this evening (RL permitting)
pete
- petebramley
- MAIW Developer
- Posts: 1529
- Joined: 17 Jun 2007, 16:05
- Version: P3D
- Location: EGBG
-
- Lieutenant Colonel
- Posts: 823
- Joined: 08 Jul 2007, 22:15
- Version: FS9
As it happens I have done some checking and found that what 1st says is correct.
I have found a few references that say that this is known bug in FS9 and can't be fixed. I have found a reference to the fact that a landclass bgl must not have a texture folder or it will memory leak and crash, and if any landclass file may not have an empty ( or underpopulated ) 'texture' folder opposite it's 'scenery' folder. or it will cause a memory leak.
Now it would seem that the only way that this could work is that if it calls no texture and there is a texture folder, the problem will happen, and if it calls for a texture not in the folder the problem will happen.
It would also explain why several sceneries that I have install have a separate folder for landclass(s) and have instructions that the landclass folder needs to be lower than the scenery in the list.
To prove this theory, or at least see if this works as a fix, can somebody that has the problem try the following :-
1. In your \Addon Scenery folder create a 'MAIW Luke AFB Landclass'.
2. Inside that create a 'scenery' folder.
3. Move the 'Luke AFB Landclass.bgl' to the newly created scenery folder.
4. Activate the 'MAIW Luke AFB Landclass' folder below the 'MAIW Luke AFB (KLUF)' folder
Then try this out. If it works we might have to think about a policy for future packages.
So who will be first to try my master plan out?
I have found a few references that say that this is known bug in FS9 and can't be fixed. I have found a reference to the fact that a landclass bgl must not have a texture folder or it will memory leak and crash, and if any landclass file may not have an empty ( or underpopulated ) 'texture' folder opposite it's 'scenery' folder. or it will cause a memory leak.
Now it would seem that the only way that this could work is that if it calls no texture and there is a texture folder, the problem will happen, and if it calls for a texture not in the folder the problem will happen.
It would also explain why several sceneries that I have install have a separate folder for landclass(s) and have instructions that the landclass folder needs to be lower than the scenery in the list.
To prove this theory, or at least see if this works as a fix, can somebody that has the problem try the following :-
1. In your \Addon Scenery folder create a 'MAIW Luke AFB Landclass'.
2. Inside that create a 'scenery' folder.
3. Move the 'Luke AFB Landclass.bgl' to the newly created scenery folder.
4. Activate the 'MAIW Luke AFB Landclass' folder below the 'MAIW Luke AFB (KLUF)' folder
Then try this out. If it works we might have to think about a policy for future packages.
So who will be first to try my master plan out?
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
-
- MAIW Veteran
- Posts: 449
- Joined: 29 Aug 2006, 16:32
- Version: FS9
- Location: LSZH