... if you search your complete folders you'll find those texture files missing.  it's because a scenery (probably, because of name) .bgl has called up the texture, which isn't there (that's why no location given - it just isn't present).  the name of the missing texture might give a clue to the .bgl. Again, that's why the black - no texture.. Possible to find copy of the missing texture in older version or FSX copy maybe, but some won't work in P3D late versions anyway.  if you do find, still need to find the right texture folder - look for terasse for example, or stick it in a lower priority texture folder.  That's if you can  of course  ;-(

 

Bingo! You are right. The two problematic texture files in my error log (Terasse.bmp, LSGK_11) are missing. :wink:

Sorry, can't seem to quote.  the texture errors mentioned by Jeff and relax  - if you search your complete folders you'll find those texture files missing.  it's because a scenery (probably, because of name) .bgl has called up the texture, which isn't there (that's why no location given - it just isn't present).  the name of the missing texture might give a clue to the .bgl. Again, that's why the black - no texture.. Possible to find copy of the missing texture in older version or FSX copy maybe, but some won't work in P3D late versions anyway.  if you do find, still need to find the right texture folder - look for terasse for example, or stick it in a lower priority texture folder.  That's if you can  of course  ;-(

Thank you, you made my day

 

The error was 

[error.18]

error=Texture t2g2.BMP failed to load (FE_REQUEST_STATUS==13)

[error.19]

error=Texture t2g2LM.BMP failed to load (FE_REQUEST_STATUS==13)

 

By chance i made a backup from my P3D V.5 setup

 

The solution 

Copy the file  t2g2lm.dds and t2g2.dds from the backup texture folder. P3D2.5/Texture to the P3DV3/texture folder.

 

For some obscur reasons those 2 files were missing while using the P3D2.5 installer for the V3

Bringing this back from ... and I know this will not be popular with those that develop products, but LM made it clear to me that errors showing up in these log files should NOT be ignored.

 

It is true that "some" of them may have NO impact, but that can also mean the product in question doesn't behave as expected.  IMHO, I'm not sure why a developer would NOT enable error logging prior to releasing their product?  It's a handy tool to catch any of errors quickly.

 

There are also many errors that do have an impact and do have performance implications.  These should be fixed by the 3rd party developer, I honestly don't understand the resistance to fixing these on future products that are identified as P3D V3.x compatible?  It's a tool to HELP developers and end users ... why wouldn't a dev want to know?

 

Sure if the product producing the errors is designed for a different verison of P3D that what one is currently using, then sure, end user will either have to accept the errors or try to fix them.

 

I run into the same issues with my daily development work (not FS related yet) and I log all my errors (visible to user or not) to log files and I do surf thru them and they have pointed out issues that I've needed to resolve (sometimes very key issues) ... there is nothing "hostile" about exposing errors, it's for the good for everyone.

 

Sorry to bring this back ... but after spending many many many many hours fixing 3rd party content, I'm probably a tad "unforgiving" at the moment.

 

Cheers, Rob.

Ditto Rob. Never had the luxury of those native ecap routines when I was coding. Ho Hum....  

It is usually simple to fix texture or effects errors.

 

The main problem is that P3D objects to taxi paths of zero width. It is necessary to use zero-width pathways when using photo textures with transparent runways to prevent the default textures apearing.

No... pretty certain L-M makes it possible to not display default textures for taxiways. I recall Scruffyduck having to release an updated ADE to address the fact that a flag for this that was ignored in FSX is no longer ignored in Prepar3D.

No, the fix was to allow the display of taxiways. I am talking about taxi paths which should never be displayed, but are, under certain conditions.

Rob,

 

If you get chance, could you see if LM could add to its log file what model or file is the source of a missing texture (or maybe I just don't understand where the entry is logged) ? I have been trying to hunt down the source of "HURON_LM is missing" for a week now using the error logging in 3.1. I'm guessing it is a night texture from an add-on boat, but I just can't find what model uses this texture.

Just do an explorer search for "huron".

 

I found all of the textures in \SimObjects\Boats\AI_At_Huron_Halong\texture

 

fenX2.bmp
feuBlanc.bmp
feuBlanc_LM.bmp
feuRouge.bmp
feuRouge_LM.bmp
feuVert.bmp
feuVert_LM.bmp
huron.bmp
huron_LM.bmp
pont_rouille.bmp
rampe.bmp
rampeUnite.bmp

 

I probably copied huron.bmp to huron_LM.bmp.

Jay,

 

_LM is usually the light map - I think

 

What route did you use to install V3.1?  Perhaps these are part of Content.msi or Scenery.msi ... and hence why V3.1 thinks it's missing (if you did just the Client.msi update route).

 

Cheers, Rob.

The texture is part of the Global AI Shipping project.