From time to time, 3rd party developers can and often will post works in progress (Hence forth, known as *WIP*) at their leisure. This serves two purposes.
#1, advertisement. It’s no secret that we use it to advertise our products. We depend greatly on this community for sales. Without it, 3rd party developers would simply dry up.
#2, feedback. This should be #1, as it truly is the most important reason why we post WIP's. We need feedback from you, the customer. As an artist, I can stare at an aircraft model for many months at a time, and still miss something as obvious as the control stick in the cockpit! That’s why we need your support to note errors.
The biggest problem most people have is how to approach a possible error when they find it without somehow upsetting the artist or developer working on the model. That is where this guide comes in.
1. First, read what the developer is posting when he post's screen shots. A lot of times he will note things that are not yet done or finished.
2. If you feel that you found an error, please research first. Find a photo or some type of reference that shows how you feel it should be.
Example. On a recent thread about the FSD/MilViz F-15, a user noted that a problem with the shape of the air brake, and attached photo's. This was fixed. No hurt feelings, and the customers get a better product. Simply saying that there is a problem helps nobody.
3. If you feel the quality of the model is not up to standard, please be specific. Comparing one product against another is not at all helpful or beneficial.
Example. On a recent thread about the FSD/MilViz F-15, users noted that the canopy frame was a little low polygon and segmented. This was noted by the developer and fixed.
Sometimes a product though simply can’t afford the cost in development other products get due to the limited market, so please understand that. Some aircraft, like the outstanding Aerosoft PBY Catalina can take years to develop, but not all developers can afford that amount of resources on an aircraft that is not as popular or may not sell well. Simply put, we can’t spend $10,000 on an aircraft if we can only expect $3000 in sales. Supply and demand. That’s why comparing X product to Y is not very helpful.
4. Treat developers with respect. Simply put, they are doing the community a service, because they want to. None of us are getting rich here. Breaking even for us is a success, and honestly, successes are getting harder to come by in this economy.
5. Don’t debate the developers over something you think is wrong, if they don’t agree. If they don’t agree, they have their reasons. If you don’t agree, vote with your wallet. Note the problem and move on.
Example. In a recent thread about the YP-23 from FSD/MilViz, someone noted a lack of weathering in the cockpit (compared to the F-15 from the same developer). The developer noted it was done due to the YP-23 being a prototype, and babied, unlike a combat aircraft. Debate should stop there. If you don’t agree, don’t buy it. Saying you don’t agree and won’t buy it is being very disrespectful to the artist.
6. Reserve judgement till it’s finished. No example or explanation needed.
With this guide, I hope I give people the courage to help us out. As long as it’s done properly, you won’t hurt anyone’s feelings. We have a small tight community, and the only way to keep it together is by helping each other, and simply being civil. Ultimately, if you don’t like it, don’t buy it.
#1, advertisement. It’s no secret that we use it to advertise our products. We depend greatly on this community for sales. Without it, 3rd party developers would simply dry up.
#2, feedback. This should be #1, as it truly is the most important reason why we post WIP's. We need feedback from you, the customer. As an artist, I can stare at an aircraft model for many months at a time, and still miss something as obvious as the control stick in the cockpit! That’s why we need your support to note errors.
The biggest problem most people have is how to approach a possible error when they find it without somehow upsetting the artist or developer working on the model. That is where this guide comes in.
1. First, read what the developer is posting when he post's screen shots. A lot of times he will note things that are not yet done or finished.
2. If you feel that you found an error, please research first. Find a photo or some type of reference that shows how you feel it should be.
Example. On a recent thread about the FSD/MilViz F-15, a user noted that a problem with the shape of the air brake, and attached photo's. This was fixed. No hurt feelings, and the customers get a better product. Simply saying that there is a problem helps nobody.
3. If you feel the quality of the model is not up to standard, please be specific. Comparing one product against another is not at all helpful or beneficial.
Example. On a recent thread about the FSD/MilViz F-15, users noted that the canopy frame was a little low polygon and segmented. This was noted by the developer and fixed.
Sometimes a product though simply can’t afford the cost in development other products get due to the limited market, so please understand that. Some aircraft, like the outstanding Aerosoft PBY Catalina can take years to develop, but not all developers can afford that amount of resources on an aircraft that is not as popular or may not sell well. Simply put, we can’t spend $10,000 on an aircraft if we can only expect $3000 in sales. Supply and demand. That’s why comparing X product to Y is not very helpful.
4. Treat developers with respect. Simply put, they are doing the community a service, because they want to. None of us are getting rich here. Breaking even for us is a success, and honestly, successes are getting harder to come by in this economy.
5. Don’t debate the developers over something you think is wrong, if they don’t agree. If they don’t agree, they have their reasons. If you don’t agree, vote with your wallet. Note the problem and move on.
Example. In a recent thread about the YP-23 from FSD/MilViz, someone noted a lack of weathering in the cockpit (compared to the F-15 from the same developer). The developer noted it was done due to the YP-23 being a prototype, and babied, unlike a combat aircraft. Debate should stop there. If you don’t agree, don’t buy it. Saying you don’t agree and won’t buy it is being very disrespectful to the artist.
6. Reserve judgement till it’s finished. No example or explanation needed.
With this guide, I hope I give people the courage to help us out. As long as it’s done properly, you won’t hurt anyone’s feelings. We have a small tight community, and the only way to keep it together is by helping each other, and simply being civil. Ultimately, if you don’t like it, don’t buy it.
