agent00729

Just an update, I think I may have solved the problem. I think the issue was with the scenery library. My layers weren’t in consecutive numerical order, and it was causing issues with Radar Contact. I fixed it and now my FSdreamteam scenery seems to load normally also. Don’t want to speak too soon, but it looks like this might’ve been the issue.

Please disregard, I got it working! The solution seemed to be changing the way I install sceneries in the scenery library. For some reason, I learned to add to the scenery library by navigating to the scenery's "scenery" folder. In this way, however, MakeRwys was unable to locate the afcad. Instead, I have to navigate to the scenery's root folder and add to the library.

Hello! I am running Radar Contact on FS9. I am using MakeRwys V4.7 (set to run as administrator, along with radar contact) and FSUIPC 3.999. My issue is that when I run Radar Contact and MakeRunwys to update the database , it doesn't update the runways for new scenery. It creates a new a4.csv and r4.csv, but the runways listed are the same as default as far as I can tell. For example, I downloaded a UAAA (Almaty) scenery with the new runways (which appear in the map and menu of fs9), but not in Radar Contact's database. This is the same issue I'm having with FSDT O'Hare. I appreciate any help in solving this issue!

Has anyone ever found a solution to this problem in Windows 7 64-bit? I tried all the fixes I read about but nothing seems to work. I also get severe stutters and jerkiness, even with a good frame rate.

Except for FSdreamteam! In their case, they updated the program that was designed for Xp/Windows 7 to 10, and now no longer works properly in XP/7. So it seems like there’s really no standard principal that developers follow, leaving consumers with adverse effects both if they upgrade the OS or if they don’t. Ironically and sadly, this practice may have the unintended consequence of propagating the very “cracks” they are seeking to eliminate.

But actually, now that I’m reading your post again, can’t you just have something like the current trial as is, and the new web interface to purchase? I know it would probably take resources to make the web interface, but it seems like something is necessary to be done to support customers who purchased at the original system requirements. Or even don’t make the interface public at all, just keep the current product as is and have a special one for support for legacy customers.

I do have PMDG, and it was working perfectly for me a couple months ago (although now that I see those posts I’m a bit worried lol). I guess this is even more of a reason NOT to upgrade my system. In any event, whatever they do isn’t justification for the principal. Anyway, I’m just disappointed that the scenery is so encumbered by the e-commerce/whatever it is that you can’t separate it from. I guess I will just have to live with having to reinstall each scenery every flight and hope that the buildings are there when I land.

I’m not sure why you are making my action (inaction) of staying with Windows 7 on my FS9 PC the issue here. That was the OS that I purchased the software for and was advertised as being supported. My system is exactly the same now as it was then. No changes on my end. Besides, FS9 is unsupported but you are still selling software for it, and its system requirements go only as far as XP. The only thing that changed was that you guys switched e-commerce platforms, thus making the scenery effectively incompatible. I have many other payware addons, and have no issues. All work with windows 7. Only FSDT I have these problems. On a similar note, I have just recently encountered the same issue with Cloud 9 KLAX that I also purchased from you guys. (I have every FS9 scenery from you except FSDT KLAX, as I have the cloud 9 one). Except the difference with this is that now not only are there no buildings, but it instantly CTD. I guess the Addon Manager is once again the culprit? In any event, it seems like we are going in circles. There must be some way to decouple the scenery from this e-commerce platform for the original OS users so that it will work properly? Via a different installation method or new installer maybe? Or the old fashioned way of just pasting the scenery and texture folders into the Addon scenery folder?

They didn’t take an action that would prohibit the software from working. In this case, you did take such an action by making a business decision to implement a mandatory e-commerce platform that doesn’t support the original OS.

I see your point with the license vs ownership. But for all intents and purposes the distinction is almost irrelevant here. I own a licensed copy of the work, not the IP itself, but it still should enable me to use the software according to the terms of the license agreement. That’s great that you have worked to get the scenery to run on new OS. But it shouldn’t come at the expense of ending functionality on the original users’ versions, it should be in addition to the original ones. This is essentially shifting the system requirements over time for the same software. FS9 didn’t stop working on windows XP when Vista came out. Microsoft Office 2010 didn’t stop working on windows 7 when 8 came out, etc. The issue here isn’t whether or not Windows 7 still works, because it does, it’s the subtle shift in system requirements for a purchased product designed and advertised to work for it.

Virtuali, I really admire your work and sceneries that make the FS world come alive. But this begs the question, why should anyone buy an FSdreamteam scenery if in a few years time when the next OS comes along, there is no guarantee that the scenery will work properly anymore? It’s more like purchasing a subscription to use for a certain period of time rather than owning the scenery.

That is unfortunate. Is there any way I can get the sceneries to work without addon manager? I understand that the circumstances around the issue are difficult, but the end result for the customer is the same: the original OS system requirements under which the sceneries were sold no longer allow the sceneries to function properly.

Also, if it doesn’t work properly for windows 7, is there any way to get it working? Since this was the OS the scenery was originally bought and supported for, it seems like it shouldn’t suddenly not be working. I can understand if it was the other way around and I couldn’t get it to work (ie, if I upgraded to windows 10 and the scenery I bought for windows 7 no longer worked, that would be my fault and shouldn’t expect it to work) but I would think scenery shouldn’t suddenly stop working on the original OS.

Ok got it. So maybe the problem was that I installed another fsdreamteam after I installed the latest addon manager? My system is still showing the latest addon manager though.

Thanks for the reply. Ok, interesting. So say even if I paste a new freeware airport from avsim into the addon scenery folder, I will need to reinstall the addon scenery manager again every time? I already have the latest one installed.