April 27, 201412 yr Hi All, After new update (2.1 build 43 ) I have a problem. Before update I have never seen something like that. Here is a screenshot about it , Şafak Çaylı
April 27, 201412 yr Commercial Member If that occurs in the day it is unlikely to be legacy. What happens in dx9? What happens in dx10 if you uninstall the dx10sf libraries? My FSX Analysis Blog
April 27, 201412 yr Author Hi , There is no problem in DX9 and DX10 without the libraries. And as I said before there was no problem "scenery fixer" previous version. I have just seen this error and just occurs LGAV with last version of scenery fixer. Thanks, Şafak Çaylı
April 27, 201412 yr Commercial Member Ok if it's ok in dx9 and dx10 without the libraries now try with the libraries installed and the general shader disabled. Depending on the results of that we look at legacy or general options My FSX Analysis Blog
April 27, 201412 yr Only popping in because I worked on that project, but sadly I can't tell you the cause. It does, however, look like the DX10 program may have caused a conflict with some anti-piracy measures - the Xs. I would suggest creating a similar post at the forum below to get a better idea of what it is that you're seeing if you run into a dead end. George would have a good idea of what you're seeing. http://www.flytampa.org/forum/viewforum.php?f=23 Anthony Cacciatore
April 27, 201412 yr Commercial Member Thanks that makes sense - that the crosses are an anti piracy measure that are being incorrectly displayed. However if it wasn't a problem in the previous version and doesn't occur with the tool enabled it must be one of the settings that is triggering it. We just need to step through slowly to identify it by disabling and enabling options. My FSX Analysis Blog
April 29, 201412 yr If you have ticked the box 8bit texture fix in general shader untick it. That causes the problem.
Create an account or sign in to comment