Jump to content

Recommended Posts

Posted

Hi!!! I have downloaded and installed Stary's Mig-19S cockpit, and found out it's notworking propperly. There's a big white area, as if there where missing LODs or TGAs or something. I have attached a photo for you to see it by yourselves. I asked Stary and he told me others have the same problem, but a solution has saddly not been found. Does any of you guys have the same porblem??? I am running merged SF2, SF2SF2, SF2E, SF2I with the 4th July 2013 patch on Windows Xp. Any idea??? It's a great cockpit, and would really like to fly in itI have the same problem with his Mig-19P cockpit, but not with his Mig-17PF one. Thatone works great!  Thanks guys!!!!

 

 

 

                     Regards, 

                                                         Ignacioc91

post-57511-0-57763100-1379540394_thumb.jpg

Posted (edited)

running out of texture memory, maybe??

or

XP and DX9 (more likely, as the lod is prolly built in max 2009, in Unicode with sf2 DX10 shaders and such??)

Edited by Wrench
Posted

SF2 with the latest patches is Windows Vista and 7 only, as XP does not support DirectX 10.  Wrench suggested that it may also be due to your system running out of texture memory.  What sort of graphics card are you running?

Posted

Ghostrider has the very same issue, I tried several things to make it disappear to no luck, even physically deleting parts of the cockpit mesh, this was still there

 

it's some odd part hidden in the model, but shoot me if I wknow which one (which I should, I build that bloody thing!)

Posted

stary did you use a object as base for an animation and forget to assigen a material to it , that could cause that

 

i had one mod where a little white square was visible , it was the object that i use for linear animation of a brake chute after assigning a material to it the problem was gone

 

the problem only appears with winXP

Posted (edited)

panel_mig19s [651 polys, 1091 verts] 'panele'

stick_base [12 polys, 24 verts] 'ERROR: No material is assigned!'

Stick [3266 polys, 2389 verts] '01 - Default'

left_pedal [176 polys, 150 verts] 'panele'

left_pedal_detail [128 polys, 258 verts] 'kokpit mig19s'

right_pedal [176 polys, 150 verts] 'panele'

right_pedal_detail [128 polys, 258 verts] 'kokpit mig19s'

front_panel_screw10 [58 polys, 80 verts] 'kokpit mig19s'

screw22 [58 polys, 76 verts] 'kokpit mig19s'

canopy_all [10300 polys, 10390 verts] 'interior baked'

 

From OUT file. 

Something wrong with stick, it's white too, as seen on the screenshot...

 

UPD: 


Air_brake_light [2 polys, 4 verts] '22 - Default'

generic_plate1 [86 polys, 52 verts] 'kokpit mig19s'

generic_plate02 [86 polys, 52 verts] 'kokpit mig19s'

new_panel-line backup [2688 polys, 1815 verts] 'ERROR: No material is assigned!'

new_panel-line copy 2 [3264 polys, 2164 verts] 'ERROR: No material is assigned!'


Edited by luk1978
Posted

stick_base [12 polys, 24 verts] 'ERROR: No material is assigned!'

 

is a dummy little box below control stick to which the latter is linked

 

new_panel-line backup [2688 polys, 1815 verts] 'ERROR: No material is assigned!'
new_panel-line copy 2 [3264 polys, 2164 verts] 'ERROR: No material is assigned!'
 
are outlines of main panel I apparently left there, must check
Posted

Yes, seems like stick_base is OK.

Both Mig-15 and La-11 cockpits have unassigned material for stick_base, but working fine...

 

I'm using Dx10 and never seen this glitch before, but switching ForceDX9=TRUE makes white parts to appear:

 

 

Posted

Moved camera to get a full view...

 

A FAT PILOT'S ASS?!!! :ohmy:

 

 

I don't know what it is...

 

 

 

Hope this will help to find that bugged part.

 

 

 

 

 

Posted

a quick temp fix is to hide the material-missing mesh parts

 

0xx  = next nunber in line

 

...

Instrument[0xx]=Hide1

 

[Hide1]

Type=INACTIVE
NodeName=stick_base

 

 

add 2 more for the panel mesh

Posted

I don't have NA, but my merged install is May2013 and it's allows Dx9.

 

Well, as Crusader said before, disabling "new_panel-line backup" and "new_panel-line copy 2" via .ini fixed the problem.

I think ini correction is enough, as it works fine now.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..