Problem with repaints
-
ahunterg95
- Posts: 29
- Joined: Sun Dec 13, 2015 11:21 am
Problem with repaints
Hi all,
I am having some issues with the Beaver and 3rd party repaints... I installed quite a few Aussie and Oceania themed repaints for the Beaver but there is a persistent issue that the right flap and right side of the elevator are showing as black on the all of the paints (from 3 different/individual painters jeansy jankees and Ron Attwood), the default Milviz paints are fine. I'm not quite sure what is going on because I have a new paint on the Otter working just fine.
First I tried clearing out the text entries in the aircraft .cfg and reentering them. No luck. Then I tried removing the texture folders and replacing with a freshly extracted texture. No luck either. Then I removed both text and texture and replaced with fresh ones. No luck. Next, I moved on and completely re-downloaded the repaint files and tried the previously mentioned steps. Still did not fix the problem. So I then moved on and completely uninstalled the beaver, reinstalled and just for good measure redownloaded the paints and placed the textures in the various beaver variants and the text in the aircraft .cfg but that also failed to resolve the issue.
I just don't know what is going on with them!
I am having some issues with the Beaver and 3rd party repaints... I installed quite a few Aussie and Oceania themed repaints for the Beaver but there is a persistent issue that the right flap and right side of the elevator are showing as black on the all of the paints (from 3 different/individual painters jeansy jankees and Ron Attwood), the default Milviz paints are fine. I'm not quite sure what is going on because I have a new paint on the Otter working just fine.
First I tried clearing out the text entries in the aircraft .cfg and reentering them. No luck. Then I tried removing the texture folders and replacing with a freshly extracted texture. No luck either. Then I removed both text and texture and replaced with fresh ones. No luck. Next, I moved on and completely re-downloaded the repaint files and tried the previously mentioned steps. Still did not fix the problem. So I then moved on and completely uninstalled the beaver, reinstalled and just for good measure redownloaded the paints and placed the textures in the various beaver variants and the text in the aircraft .cfg but that also failed to resolve the issue.
I just don't know what is going on with them!
-
doodlebug
- Posts: 1642
- Joined: Sun Feb 19, 2017 2:49 pm
- Location: LYX>YUL
Re: Problem with repaints
Do you have the latest version [171229]. The initial release used a different paint configuration.
-
ahunterg95
- Posts: 29
- Joined: Sun Dec 13, 2015 11:21 am
Re: Problem with repaints
Ahh bummer, yep I am on 171229... So that is the problem, the paints have fallen out of date with the current version! 
At least I can stop turning myself inside out, thankyou!
Is there anything that can be done from my side to adjust something to get the paints working again?
Andrew
At least I can stop turning myself inside out, thankyou!
Is there anything that can be done from my side to adjust something to get the paints working again?
Andrew
-
doodlebug
- Posts: 1642
- Joined: Sun Feb 19, 2017 2:49 pm
- Location: LYX>YUL
Re: Problem with repaints
I think the paints were fixed quite quickly, so this may not be the issue. NB: The original paintkit used a symmetrical configuration.
-
ahunterg95
- Posts: 29
- Joined: Sun Dec 13, 2015 11:21 am
Re: Problem with repaints
I've just had a look on the OZx forum, most of the paint downloads/uploads date back to June-August 2017, so before most of the updates and especially way before the latest 171229. Unfortunately, I think it may be the issue.
-
Timmy74
- Posts: 74
- Joined: Sun May 28, 2017 7:54 pm
Re: Problem with repaints
......so do the old third party paints work now with the latest update 171229.....?ahunterg95 wrote:I've just had a look on the OZx forum, most of the paint downloads/uploads date back to June-August 2017, so before most of the updates and especially way before the latest 171229. Unfortunately, I think it may be the issue.