So is there something going on with my ISP? I have had FS Repaint v2 for a LONG time.So what is the reason I see FS Repaint v2 released on the opening web page??????

I get the sense that someone on the editorial staff is just regurgitating any press release that Abacus sends without considering the context. In Avsim's 10+ year history, this happens from time to time. Obviously, the story just needs to be deleted.

Same here. Just checked I have V2.04.52. Bought it almost 2 years ago. For a minute I thought I had V 1. Must be the same thing that happened with the dreamliner release.

I'm sure it's an honest/innocent mistake.

For those who have it, does it work with other payware airplanes? I am looking for a good "painting for dummies" kit to do some simple repaints.

Abacus sent out an e-mail to its customer base promoting FS Repaint 2. (Not a new release, etc.)An AVSIM editor must have received it and posted it as a "release".No new version, etc., no "regurgitation" of a non-existent press release.Hey, it's a slow news day.

Very slick way for Abacus to get free advertising.

Well, yes and no. Version 2 has been out a very long time. However, the original version 2 did not work properly with FSX under Vista. In fact, when you executed the program the system displayed an error message. After many months and a ton of e-mail traffic back and forth with Abacus, they provided a newer version that now works properly with FSX. The Version number is 2.10.53, build 322. Check your version number. If it does not correspond with the numbers here, you need to get a new download. Note: I didn't see any message traffic from Abacus on this newer version.One caveat - the version I have will not work with the path aliases in the fsx.cfg file. For example, if you have your AI aircraft in a different directory from your "flying" aircraft (default placement in simobjects\airplanes) FSRepaint will not display any repaints in the left window. It will show the directories but no texture sets. My workaround is to take an AI aircraft folder and copy it to the "airplanes" folder and work on a texture set from there. Then, just copy out the new texture and delete the remaining files.Note: The developer of FSRepaint must have started work on the path alias problem because the additional directories show up but no textures display.fb

One caveat - the version I have will not work with the path aliases in the fsx.cfg file. For example, if you have your AI aircraft in a different directory from your "flying" aircraft (default placement in simobjects\airplanes) FSRepaint will not display any repaints in the left window. It will show the directories but no texture sets. My workaround is to take an AI aircraft folder and copy it to the "airplanes" folder and work on a texture set from there. Then, just copy out the new texture and delete the remaining files.Note: The developer of FSRepaint must have started work on the path alias problem because the additional directories show up but no textures display.fb

FS Repaint V2 will display aircraft in the non-default directory as long as that directory is inside the default directory. Confused yet?If you add an aliased directory such as "AIaircraft" then it will work if that directory is inside the simobjects\airplanes directory. So simobjects\airplanes\AIaircraft would work, but simobjects\AIaircraft would not. Lukily, FSX doesn't care if the aliased directories are inside the simobjects\airplanes directory or not as long as you put the correct path in the config file. I put all my non-FSX-default aircraft in two directories, "SimObjects\Airplanes\Add-on_Aircraft" and "SimObjects\Airplanes\AI_Aircraft". Only the default aircraft are in the "SimObjects\Airplanes" directory so my two addon directories show at the top of the list making it easy to keep up with. Here's what it looks like:

FS Repaint V2 will display aircraft in the non-default directory as long as that directory is inside the default directory. Confused yet?If you add an aliased directory such as "AIaircraft" then it will work if that directory is inside the simobjects\airplanes directory. So simobjects\airplanes\AIaircraft would work, but simobjects\AIaircraft would not. Lukily, FSX doesn't care if the aliased directories are inside the simobjects\airplanes directory or not as long as you put the correct path in the config file. I put all my non-FSX-default aircraft in two directories, "SimObjects\Airplanes\Add-on_Aircraft" and "SimObjects\Airplanes\AI_Aircraft". Only the default aircraft are in the "SimObjects\Airplanes" directory so my two addon directories show at the top of the list making it easy to keep up with. Here's what it looks like:

Perhaps that will work. However, in my case your example does not allow the management of AI aircraft. You see, I have approximately 400 aircraft types and over 7,000 texture sets. Placing all of those aircraft in a single folder would make my situation a nightmare. You see, I have my AI aircraft in a directory (c:\fsx\simobjects\ai) that contains 57 folders with folder titles identifing the developers of the aircraft. For example, in my fsx.cfg file I have path aliases identifying the aircraft's developer:SimObjectPaths.6=SimObjects\AI\AFXSimObjectPaths.7=SimObjects\AI\AIASimObjectPaths.8=SimObjects\AI\AIGSimObjectPaths.9=SimObjects\AI\AIMALSimObjectPaths.10=SimObjects\AI\ANZSimObjectPaths.11=SimObjects\AI\BAUSimObjectPaths.12=SimObjects\AI\BROSimObjectPaths.13=SimObjects\AI\BUCSimObjectPaths.14=SimObjects\AI\BURSimObjectPaths.15=SimObjects\AI\CANSimObjectPaths.16=SimObjects\AI\CASSimObjectPaths.17=SimObjects\AI\CDAI...and the like.Within each subfolder are all the aircraft I have for that developer. For example, in the "AIA" folder I have:Boeing B737-300LogoLight V2 AIABoeing B737-300Normal V2 AIABoeing B737-300W V2 AIABoeing B737-400 AIABoeing B737-400LogoLight V2 AIA...and the like.Within each of these folders are the texture sets, model folder, *.air file, and aircraft.cfg files.Now, FSRepaint displays the subfolders (see above - example CDAI) but there are no aircraft in these folder displays. It appears the developer made a start at implementing the FSX path aliases but didn't complete the project.fb