f-86F

[VIKBELL]

I have problem with the mirror in the F-86f it shows a circuit board..

[Evilducky]

Can confirm this as well. I notice that today too.

[NineLine]

Hey guys, cant reproduce here, can you try running a repair and see if that helps?

[Evilducky]

Fresh install of the F-86F, but sure, Ill repair it.

[NineLine]

My test version is showing this, so maybe it is an issue, can you guys tell me what other modules you have installed?

[Evilducky]

all but the 190 and the mi8

[NineLine]

Well I had it on my test version for a bit, but now its fine, so not sure what is going on. I did uninstall the F-86 (from the module manager) then reinstall... first launch it was still incorrect, but now it seems fine. Perhaps try reinstalling? Doesnt make much sense....

[Evilducky]

No luck on the unistall / reinstall on the saber.. same thing.

 

Edit - This is only affecting the Saber. Did a few other aircraft and they do not get that. Checked the Open alpha and there is no issue.

 

2nd Edit.. I wonder if this has something to do with the copy protection. I just unistalled / reinstalled again, this time wiping the saber files and when I try to activate it, I get an error message that the serial number is incorrect, but when I got into the mod manager, the SN is there. This happened when I was reinstalling the modules this morning as well.

Edited December 31, 2015 by Evilducky

[NineLine]

No luck on the unistall / reinstall on the saber.. same thing.

 

Edit - This is only affecting the Saber. Did a few other aircraft and they do not get that. Checked the Open alpha and there is no issue.

 

2nd Edit.. I wonder if this has something to do with the copy protection. I just unistalled / reinstalled again, this time wiping the saber files and when I try to activate it, I get an error message that the serial number is incorrect, but when I got into the mod manager, the SN is there. This happened when I was reinstalling the modules this morning as well.

 

Not sure, I am not exactly sure why mine is fine now...

[SkateZilla]

turn off mirrors in options.

 

close dcs,

 

launch dcs, re enable mirrors

 

load mission with f86

 

report.

 

i think there was another thread in the BST section about this, possible texture memory loading/caching issue.

Edited December 31, 2015 by SkateZilla

[SkateZilla]

http://forums.eagle.ru/showthread.php?t=155974

[Evilducky]

Hey, that worked! That's a weird bug.

[NineLine]

It should probably be reported at any rate, but glad there is a work around for it.

[SkateZilla]

havent been able to re-produce it at all.

[NineLine]

havent been able to re-produce it at all.

 

Yeah, thats the problem, I had it on one of my test versions, but since it went away I havent been able to un-fix it, possible its something that once corrected is good to go from here on out, maybe something left over from a previous version.

[Evilducky]

It might be.. But I was digging through the files trying to find something and nothing seemed out of wack (comparing it to the open alpha version).

[SkateZilla]

thats why I assume its just a old cached shader or texture somewhere that gets flushed when mirrors setting is cycled.

[gospadin]

FWIW, I had the same issue with the Mi-8 when I first installed 2.0 alpha. The disable/re-enable worked just fine.

[VIKBELL]

turn off mirrors in options.

 

close dcs,

 

launch dcs, re enable mirrors

 

load mission with f86

 

report.

 

i think there was another thread in the BST section about this, possible texture memory loading/caching issue.

 

 

I did not have mirriors on however turned them on and followed instruction and it was reset thank you.

Edited January 1, 2016 by SkateZilla

[HeadHunter52]

Mine runs fine.

Other modules are Huey, Mustang and FC3.