Page 2 of 3

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 04:22
by Airspeed
GHD wrote:FSXA.

Two missing textures:

FULMAR-EXTCOCKPITS_T.BMP

FULMAR-INT_T.BMP
How do you know that they are missing, George?

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 08:56
by DaveB

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 09:48
by GHD
Yep:

ShowMissingTextureAlert=1

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 11:40
by Airspeed
I watch, I try to learn!
I copied & pasted from DaveB's link.
My FSX.cfg, located in SAFETYFSX directory now includes:

[SCENERY]
LENSFLARE=1
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=4
// To show alerts or areas, set to = 1
// To hide alerts or areas, set to = 0

// Alert for missing textures
ShowMissingTextureAlert=1

// Alert for missing objects
MissingLibraryAlert=1

// Render Trigger areas as visible boxes
ShowTriggers=1
I ran FSX, loaded the Defiant, but it didn't throw up a trigger message or Alert in the sim.
So I searched my computer for text including the missing text names, and all it found was the actual Fulmar .bmp.
Please tell me then, where is the trigger message or Alert saved to or displayed? It must be somewhere, for George to have seen it.

A second brand new concern for me is this:
I add a part "MIKE" to a sim object, and apply "GHD.BMP" as the texture.
I decide that "MIKE" is not really appropriate, so delete it.
I understand that this will cause a very slow load and all sorts of scary possibles, because FSX insists on trying to attach GHD.BMP to the non-existent part.
So, I delete GHD.BMP; I get the ugly feeling that FSX still carries that instruction to find a non-existing texture, and attach it to a non-existing part. :worried:
And I can only find it by magic spell, or hex, as they describe it? :doh:

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 11:51
by GHD
This is how it displays:

Image

You can also open Defiant.mdl in Notepad and search for "FULMAR".

You can also open the nodel in ModelConverterX and it shows the missing texture:

Image

In fact the textures are not used, but FSX wastes time looking for them.

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 13:05
by Airspeed
Thanks George, I've seen similar dialogue boxes pop up previously, but not for the Defiant.
Did I download a different version?
Searching that .mdl for FULMAR discovers no results.
After midnight, I'm off.

EDIT: SEE POST 11th March :cpu:

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 17:28
by Dev One
Could it be because of the FSX glass mod?
Keith

Re: B.P. DEFIANT BETA TEST TIME

Posted: 10 Mar 2016, 20:37
by Molyned
Thanks folks :agree: all your comments have been very useful and will be rectified where possible. I've received some useful modified config files from Keith and I'll be testing them pronto.
I'm perplexed about the missing textures stuff - I don't see that in FSX sp2 (don't have acceleration installed). I did merge a few objects from the Fulmar cockpit and at that time a bunch of Fulmar files were in the texture folder - since deleted as 'not needed'. I think I'll just add dummies of the two named files.
BTW - If you've got my Fulmar installed you could copy the two offending texture files into the Defiant texture folder - might work.
I'm planning to include a target tug varient on the published aircraft - lots were used forthat purpose.
Cheers :cheers:
Dave M(oly)

Re: B.P. DEFIANT BETA TEST TIME

Posted: 11 Mar 2016, 03:34
by Airspeed
Don't hit me, George! :worried:
Thanks for the suggestion Keith. ;)
In bed, it dawned on me that the fsx.cfg that I modified, was in FSX SAFETY. I should have fixed User\....appdata.....etc!
SAFETY was a folder I created many months ago to hold copies of stuff while I was being guided through experimental changes by Rohan.

Now that I've amended the correct copy, I'm getting the alert. :cpu: :agree:

:doh: But before I had even gone to select the Defiant, I was presented with about 20 missing objects each with its own cute 35 character name.
I wrote details of the first four, so that I can try to find them; possibly the bits of Payware Barra that I didn't like.
This was my second concern spelt out above. If so, I'll need to learn about that hex editing trick, or live with the knowledge that I'm carrying a swag of dead weight.

Re: B.P. DEFIANT BETA TEST TIME

Posted: 11 Mar 2016, 04:11
by Airspeed
DaveM;
you say ".....textures stuff - I don't see that in FSX sp2 (don't have acceleration installed). I did merge......"
Do you have those alert & trigger lines in your fsx.cfg?
If not, use DaveB's link, copy the lines below [SCENERY], then go to your fsx.cfg .Scroll down to [SCENERY] and paste them below the lines already there.
The location has been posted on various topics on this Forum, but it won't hurt to repeat:
Users\User(may="yourname")\Roaming\AppData\Microsoft\FSX
It has opened my eyes (see above) and probably explains why FSX takes so long to load up for me.
Thanks for the Defiant. I loved the 1/72 Airfix kit, and I'm loving yours. :thumbsup:

EDIT 18:25hrs.....Aaaarghhh! none of them can be found on my computer. :help: I'll look on line and see if they pop up. :|
edit 18:33hrs..... :help: could.t turn up any on the net either. Weird.