• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

No idea!

  • Thread starter Thread starter Aviasim
  • Start date Start date
Just to keep this going, but you chaps are not going to believe this...

First they crucify me, then stomp me into the ground by telling me that my scenery sux and that they will never buy it again. I can handle that with my thick as leather skin :rolleyes:, but and now for the shock :confused:; they want me to fix it! :eek::eek::eek:

I can only laugh... Crying will not help. Maybe shouting; I may sell a few records that way and get rich!

Talk about the opinions of 12 year old boys! :D
 
Hi

I've always built freeware scenery and have had some quite irritating emails in the 10 or so years I've been building stuff for FS. I've learnt the following.

  • Reply with basic question which try to resolve the issue, ignoring the users nasty approach.

  • never retort, you should always step above it, never stoop to the same level as the user.

  • If the first reply doesnt work then ignore any futher emails from the user...we have better things to do with our time :D (maybe not possible when dealing with payware, LOL)

In terms of receiving emails about missing things or things that maybe arent quite correct or performance related emails, I always welcome those types of emails because it will benefit everyone. We usually use beta testers to do this usually people who know the airfield as with Duxford we had a very helpful chap who helped with all sorts of things for us and lived local to the airfield and knew it well and the feedback is always constructive.

But even emails from general users after release are 99% of the time constructive and very helpful you may get one or two who think they have a right to speak to you the way they do for what ever reason but it don't wash with me. I'll reply once but if they continue, as I say above, I'll ignore him/her. If you cant be civil and polite which costs nothing then dont email me I say!! (it takes more effort to send an angry email as it takes more thought)

I always find these days that the good comments far out weigh the bad ones so the bad ones dont warrant any type of wasted emotion.

My stance on payware is this...If I buy something for FS then I want it to work on my PC, I dont want to have to go out and spend a fortune on computer parts to get the best out of it (I would expect the airfield/s, aircraft/s to be top notch optimised and usable especially when I'm parting with my money). I certainly dont have an all singing all dancing PC to design on (and certainly dont have the money to spend on one) my Pc is in fact a very average PC with onboard graphics but going back to freeware for a moment having an average PC benefits our ACG's users because our scenery is designed to work well on a wide range of PC's which is what we want to get the most users happy with it. Duxford was designed on a single core PC with 2Gb of ram and is detailed enough for flight simulator. Building with performance in mind is very important. Yes you can go and throw as many polygons, texture vertices and large textures sheets as you like at a model but you have to ask does it really need it in terms of what it is.

We have to remember that FS isnt a architectural program it's a flight sim to fly in, the airfields to most users are secondary to the aircraft you fly. If a developer is going to sell a product then it has to meet all their customers PC's requirements, yes that means the lower end PC's too otherwise a large proportion of users will be missing out as will the developer in terms of £'s, $'s etc.

;)
 
Last edited:
My stance on payware is this...If I buy something for FS then I want it to work on my PC I dont want to have to go out and spend a fortune on computer parts to get the best out of it.

You've mentioned a critical point there regarding performance on less than new computers...

In fact, that's the very reason why everytime I replace my "flightsim computer" with something newer and faster, the one being replaced is moved down the food chain on my network.

I currently have three generations of machines ranging from a lowly...

AMD Athlon LE-1640 2.6 GHz, 4GB RAM Vista x32 SP2

to my newest...

Intel i7 2600k OC 4.4 GHz, 8GB DDR3 Win x64

This allows me to check every project's performance on a variety of machines as a "sanity check." :D
 
I released a freeware mesh set for CFS2. It uses SRTM, Canadian data, and other odds and ends I have collected.

It covers all of the world at LOD7 and the WW2 theater of operations at LOD8. Included was a set of land-water masking for the entire planet, to replace the crude set that came with the sim. The mesh can be used in CFS2->FSX, if desired.

I did the mesh set because at Simviation, they hosted a mesh set that was extremely poor in quality. The developer had no idea what he was doing, and never even checked his work in tmfviewer...which showed gaps between all his mesh sets. The mesh also suffered from the FS2000 resample bug that doesn't build the correct lat-long position in the header, sometimes leading to mesh not even showing up in the sims.

Many CFS2 simmers were using this poorly made mesh, and my pleas with Simviation to remove it were never answered. So I made my own set. The land-water masking was needed as well, as the default CFS2 masking was made before SRTM and LandSat data were available. The old "Digital Chart of the World" data was used. As a result, the default CFS2 world, and many subsequent addons are mislocated.

The criticisms ranged from 'Sidney looks like it's underwater" to " there aren't any coastlines".

Would anyone have any idea how difficult it would be to make beaches for the entire planet in CFS2? Well... maybe 10 people. As far as Sidney, I suggested the masking was better than the default masking, and was mechanically produced with Slartibartfast... the user was more than welcome to make a new custom mask, and I'd include it with the set, and credit him with the fix. No reply.

Others just didn't like the masking because much of the default and addon airfields were partially submerged. I explained this is because they were misplaced... my masking was at least 95% correct... much better than the default.

When users started to NOT use the masking, they complained because the mesh was "off". Again, I had to explain the default mesh and masking were wrong... which is why I did the masking in the first place. The mesh was right, it was the default masking that was wrong. Most people could not accept that Microsoft would release a sim with faulty data.

Many users stubbornly still use ( and recommend ) the Simviation mesh set, even after I proved it was inferior to the default CFS2 mesh.

As the above stories indicate, the criticism was from unknowledgeable people. They had no idea of the labor or technical difficulties. Most users did not complain, and some actually have understood the newer mesh and masking is much closer to reality than the default. I'm not convinced anyone really believes me when I tell them the Simviation hosted mesh is terrible.

Currently I'm playing with ASTER GDEMs, and I may eventually release a set at LOD9. Technically, there are some problems, and some areas will need to be patched with resampled SRTM, NED, or other data sets. Water-masking will need to be reapplied. Maybe I'll just let Justin Tyme deal with the complaining. I fear ever releasing the set, for the ridiculous comments I'll receive from ignorant end-users.

But then again, in many areas of simming, I'm the ignorant one... Thick skin, and a chin up is good advice for all developers.

Dick
 
Talk about needing thick skin, I was just thinking of all the ridicule and extremely harsh statements about MS Flight (even myself tends to be a critic as I usually call it "MS Flighty"). Man, I would hate to be a developer on that reading the 100's of mean comments. They are human too with feelings... just doing their job.

just came to mind as I read this thread...

Clutch
 
"They are human too with feelings... just doing their job".
I feel pity for them because they will probably be unemployed very soon unless Microsoft comes up with something we do not know about yet?
But, I am sorry, this is besides the point.
I think, that (at least for freeware,) developers should include some of their source files in the download so that others can adapt them to their own wishes because if they do not, they do the same thing as MS is apparently intending on doing with Flight i.e. making it impossible to add your own modifications.
In the case of payware developers, I'd say, why do you not add some possibilities as well for those that are not pleased 100% with your scenery to make some changes? That way you can reply to those remarks with: 'here you go, here are some source files, make it anything you like?'
So make it some kind of 'open source' in certain (minor) aspects.
Just an idea.
 
Last edited:
"They are human too with feelings... just doing their job".
I feel pity for them because they will probably be unemployed very soon unless Microsoft comes up with something we do not know about yet?

Roger that. I feel bad for them. FSX was a real mess also when it came out, and people were pretty upset.

In the case of payware developers, I'd say, why do you not add some possibilities as well for those that are not pleased 100% with your scenery to make some changes? That way you can reply to those remarks with: 'here you go, here are some source files, make it anything you like?'
So make it some kind of 'open source' in certain (minor) aspects.
Just an idea.


I did this once, with a freeware package. I gave the source files out with the F-136, a flying carrier 'scenery' that you could place all over the world. Included the Gmax file. Months later, someone came out with it again, saying he had created it, lol... I thought it was a bit funny.

Another person talked me into giving them one of my older files and I find out he is going to 'fix' it and make a really nice payware of it. That kind of felt weird.

I dont know that sharing source files is always good, though if they really wanted them, they can get them, with alot of work.


Bill
 
"They are human too with feelings... just doing their job".
I feel pity for them because they will probably be unemployed very soon unless Microsoft comes up with something we do not know about yet?
But, I am sorry, this is besides the point.
I think, that (at least for freeware,) developers should include some of their source files in the download so that others can adapt them to their own wishes because if they do not, they do the same thing as MS is apparently intending on doing with Flight i.e. making it impossible to add your own modifications.
In the case of payware developers, I'd say, why do you not add some possibilities as well for those that are not pleased 100% with your scenery to make some changes? That way you can reply to those remarks with: 'here you go, here are some source files, make it anything you like?'
So make it some kind of 'open source' in certain (minor) aspects.
Just an idea.

I think thats quite a good idea, obviously I in the case of scenery, not your entire GMAX file, but a small specimen of what they want changing. Hmm, my own "SDK" for my scenery now there's an idea :p
 
No significant source files shared. Hardly ever with someone I don't know.

I like sharing knowledge. Don't like handouts and theft.

A spoon with which to feed, rather than spoon fed.

Sent from my mobile .. words substituted by iPhone at will.
 
Back
Top