Jump to content

robmw

Members
  • Content Count

    18
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

21 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, this is how ACM is intended to be used by developers, just to include their autogen definitions in a folder under their scenery which is then merged with all the others to create the required files in the sim's default autogen folder. The fact that ACM can also handle duplicates enables it to work as discussed here. ACM actually uses the SDK tools (spb2xml) to do some of the conversion work behind the scenes. I've made the effort myself for some add-on scenery products to extract and compare autogen definitions from the default autogen files before and after installation to see exactly which autogen definitions have been added. I then put just these definitions into a folder under the scenery for ACM to use, effectively doing some of the developer's work for them. Yes, it is tedious and not for the faint-hearted but something I thought worth doing when I realised it was possible. Rob
  2. I'm not sure about the flipped dds textures now - the problem may be with FS Repaint which is quite old now. I've looked at the same textures in ModelConverterX and they appear ok with the switch to flip textures set off by default. In addition some of the texture folders have both bmp and dds present for the same texture and the bmp is being used in preference. My comments about missing models and textures still stand though and I'll try to start fixing these. I've so far found cases where textures for the wrong variant are present (e.g. B737 textures in B727 texture folders) and where the wrong model is specified in the cfg file. The latter are easy to fix once found. It will be the case that these problems are not showing up if the problem variants are not actually used in any schedules so what I'm doing might be unnecessary.
  3. Has anyone else noticed any of the texture issues I think are present? As an example the UTT B787 has a number of flipped dds textures. It looks as if bmp textures were converted directly to dds without compensating for the fact that bmp textures are flipped internally by the sim before display. It's only some of the dds textures but I've found quite a few so far as there are such a large number of additional aircraft in Pete's updates! I think I can pinpoint missing models and textures automatically but the only way to find the flipped textures is by eye going through all the variations using a tool like FS Repaint. It would be very time consuming doing this in the sim as you'd need to make sure a schedule was active with the aircraft you want to see. That might be why there haven't been many comments from elsewhere as you'd have to be in the right place at the right time to notice the missing / flipped textures?
  4. Hi Pete, I think I've found an error with the AIA Westjet 767 which would have prevented it displaying. The cfg file specifies the PW model but the actual textures are labelled for the GE model so I changed the cfg file to point to the GE model and the livery displays in FS Repaint at least. Perhaps this was the problem? In the course of optimising the textures I've come across quite a few aircraft where the cfg files point to the wrong models or texture folders preventing them from displaying. Also a number of DDS textures appear to be flipped so not displaying properly. I need to write something to scan through all the aircraft folders to pinpoint the above which should make it easier to go in and fix the problems. Could you PM me a link with your latest update from last week please so that I'm working with the latest version. Thanks
  5. I've used Nick's setup guides for each system I've built since early 2007 with great success. The rationale is to squeeze the best possible performance out of well-specified hardware, and yes all the steps need to be followed in the correct order to work as intended. The thing that convinced me that his advice was worth following in the first place, and continues to be so, is that he properly explains the how and why of each step in some depth without being too technical or relying on too much jargon. He also explains clearly how these steps relate to the working of the FSX engine and why they help with performance. His latest guide, although dealing in some detail with current generation hardware (Haswell, GTX780 etc) still has much generic advice which will remain true into the forseeable future. Rob W
×
×
  • Create New...