Junkyard syndrome

[Boikat]

Does anyone know of a fix for this?

[Mitch.]

I had a similar problem about a year ago when I had my old graphics card. I got the same effect but across all my aircraft, poor defualt Cessna:



I, for the life of me, cannot remember how I fixed the problem. Sorry mate. Perhaps installing the latest drivers?

[grizzard]

I had a similar problem and effect a while back.  The wings were attached vertically, pilot fell out the bottom, and various components in a state of explosion.  In my case it was a driver problem. I went to the driver ver that Nick had suggested and have not had a problem since.

[Boikat]

Thanks guys!

[SubZer0]

Do you have a BUFFERPOOLS entry in your .cfg? Too high a number in that entry can cause this.

[EJW]

Call that a junkyard?

[EJW]

Call that a junkyard?

It's not like that in flight, just on the menu. Strange!

[basys]

Hi Folks

Boikat -
Objects rendered as disassociated components occur as a result of a render stall.

The render stall can have several root causes -
- Sliders too high
- Inapropriate/bad modeling techniques
- Inapropriate/bad texturing techniques
- Missing Textures
- Missing/incorrect texture.cfg file
- texture.EXT called by the model, differs from that present in the repaint folder.


As your errors are occuring on repaints of default aircraft, (i.e. well optimised models),
and does not manifest itself on the default paints,
then please see the following links for the likely cause -

FSDeveloper - Wiki - Missing textures

FSDeveloper - Wiki - Texture.cfg (FSX)



HTH
ATB
Paul

[Boikat]

Do you have a BUFFERPOOLS entry in your .cfg? Too high a number in that entry can cause this.

I did not see one.  What [heading] is it under, if there is one?

[SubZer0]

Do you have a BUFFERPOOLS entry in your .cfg? Too high a number in that entry can cause this.

I did not see one.

[SubZer0]

Do you have a BUFFERPOOLS entry in your .cfg? Too high a number in that entry can cause this.

I did not see one.  What [heading] is it under, if there is one?

It's one that you add yourself.. It would look like this:

[BUFFERPOOLS]
PoolSize=

Because you don't have it in there, it can't be that. It could be, as basys pointed out, sliders too high or simply bad texturing techniques.

[Boikat]

Hi Folks

Boikat -
Objects rendered as disassociated components occur as a result of a render stall.

The render stall can have several root causes -
- Sliders too high
- Inapropriate/bad modeling techniques
- Inapropriate/bad texturing techniques
- Missing Textures
- Missing/incorrect texture.cfg file
- texture.EXT called by the model, differs from that present in the repaint folder.


As your errors are occuring on repaints of default aircraft, (i.e. well optimised models),
and does not manifest itself on the default paints,
then please see the following links for the likely cause -

FSDeveloper - Wiki - Missing textures

FSDeveloper - Wiki - Texture.cfg (FSX)



HTH
ATB
Paul

Thanks. I'll have to look into that too.  (Unfortunatly, I must now run so,e errands, then mow the lawn.  RL bites, at times....)

[crazyhorseabg]

I had that problem with my f 16 patch. But only when running fsx sp 2.
whish you luck solving the problem.

[Brett_Henderson]

Hi Folks

Boikat -
Objects rendered as disassociated components occur as a result of a render stall.

The render stall can have several root causes -
- Sliders too high
- Inapropriate/bad modeling techniques
- Inapropriate/bad texturing techniques
- Missing Textures
- Missing/incorrect texture.cfg file
- texture.EXT called by the model, differs from that present in the repaint folder.


As your errors are occuring on repaints of default aircraft, (i.e. well optimised models),
and does not manifest itself on the default paints,
then please see the following links for the likely cause -

FSDeveloper - Wiki - Missing textures

FSDeveloper - Wiki - Texture.cfg (FSX)



HTH
ATB
Paul

If it were "hard" errors.. i.e. cfg syntax, or physically non-present textures, it would manifest itself on all computers.

It seems to be animated parts only, and in the past, this has been a hardware problem (software if consider drivers software). It's kinda like the video-card is overwhelmed, and "decides" that it's just gonna render animated parts as static.. not even ATTEMPT to render-re-render them through their animation, above and beyond the models motion as a whole.

The "easy" solution is a high-end video card

[Boikat]

Hi Folks

Boikat -
Objects rendered as disassociated components occur as a result of a render stall.

The render stall can have several root causes -
- Sliders too high
- Inapropriate/bad modeling techniques
- Inapropriate/bad texturing techniques
- Missing Textures
- Missing/incorrect texture.cfg file
- texture.EXT called by the model, differs from that present in the repaint folder.


As your errors are occuring on repaints of default aircraft, (i.e. well optimised models),
and does not manifest itself on the default paints,
then please see the following links for the likely cause -

FSDeveloper - Wiki - Missing textures

FSDeveloper - Wiki - Texture.cfg (FSX)



HTH
ATB
Paul

Tried the sliders, no change.
Checked everything I could check on the textures, the componants are all there, all have the same nmaes coresponding to working textures.

Had a busy day, so I'm checking the links now.

Thanks!