• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

navigation lights

Spad54

Spad54

SOH-CM-2025
We're hoping that someone will be able to shed light on a solution to a problem we've encountered with our next project, the Boeing Stearman fully compatible with P3D V4. One of our testers is reporting that he is able to get navigation lights visible in his installation. The lights are 3D modeled using an attachpoint to cause the lighting effect to be visible at the light lens location. It uses effects files that are located in the main Effects folder in P3D and a .bmp file that is located in the Effects Texture folder. Others on our team using P3D V4 are not able to reproduce this problem, reporting that lights are working on their installs. Do any of you know of what might block the lighting effect in P3D V4? Your assistance will be greatly appreciated and if one of you points us in the direction of a solution we'll comp with a copy of the completed project. By the way he has the add-on Chase Plane installed as well Thanks
 
P3D is using a different order of priority than FSX when common folders are concerned. As you mention that a bmp file in the effects folder is used, you may wish to check if there is a conflict of filenemes with a bitmap present in another folder having the same filename. To rule this out I would suggest renaming the bmp to something very unique and specific and make sure the correct filename is referenced in the effects text file.
 
Dimus said:
P3D is using a different order of priority than FSX when common folders are concerned. As you mention that a bmp file in the effects folder is used, you may wish to check if there is a conflict of filenemes with a bitmap present in another folder having the same filename. To rule this out I would suggest renaming the bmp to something very unique and specific and make sure the correct filename is referenced in the effects text file.
Click to expand...

That's a great thought and I'll try that straight away. I'll let you know the outcome
 
Spad54 said:
That's a great thought and I'll try that straight away. I'll let you know the outcome
Click to expand...

That did not correct the problem but in testing helped me discover the effect file may have been the problem all along. I need to test further but if indeed that turns out to be the case, we have solved the problem and I'll be sure to let you know when the model is ready and get you a copy. Many thanks
 
Just another thought, I don't know how useful: does the person with the problem have the plane installed in an
outboard .xml folder, whereas all the other testers have theirs installed in the v4 main folder?

I ask because I had a problem with the vc click sounds not working in the Phantom when I tried to install in my
outboard .xml folder. Moving to the v4 main folder solved that.

- RobM
 
RobM said:
Just another thought, I don't know how useful: does the person with the problem have the plane installed in an
outboard .xml folder, whereas all the other testers have theirs installed in the v4 main folder?

I ask because I had a problem with the vc click sounds not working in the Phantom when I tried to install in my
outboard .xml folder. Moving to the v4 main folder solved that.

- RobM
Click to expand...

No that was not the case. Turns out that when I did as suggested and modified the bmp file to a unique identifier and then modified that fx file it killed the effect. That making no sense caused me to go back to my PartsDataDef file to crosscheck the effect name associate with the attachpoint and low and behold it was not the effect I was using. The red herring that preventing my discovery is that other than this one tester all others have all of the previous effects files installed from previous projects that this tester did not. Changing the .bmp file name sent me down the path to solution. Just waiting to hear from the fellow with the issue to see if he indeed now has the effect working. If not I'll be back Thanks
 
You must log in or register to reply here.
Back
Top