Tym, I'm going to try your suggestion. I assume this applies to the beacon and nav lights as well?

 

I have no issues with navs and beacons in my install, only the strobes appear to be a fraction of the size of other lights. Of course, you can try a similar approach with other lights if they're problematic, but test with the strobes first and definitely keep backups of the original files... :wink:

 

Tym

Rob, 

 

are the default clouds also white in the middle of the night? 

Why is it that some people appear to have working strobes and navigation lights on AI planes, and yet a large number of us see nothing? :huh: Or are the people with working strobe lights talking about user aircraft rather than AI?

That's not correct. It can be fixed very easily by having  the 2.5 installer (or the user) add symbolic links to the Prepar3d main folder, for each of the configuration files that have been moved to PROGRAMDATA.

 

Well we dont know that the links won't be in the install. Even if not, you bring up an excellent point. Doesn't make sense though, that LM would allow the sim to break the user experience.

It is a humorous scenario that the terrain shadow bug needs to be proven (here and in the LM forum) again and again, even when the new version is about to come to the limelight. It's a fact, easy to reproduce, it just seems the testers are hardly know how to find those problems, rather, some of them often try to prove a mentioned problem didn't exist, just because they personally have never come accross it during their happy flights.

 

This attitude is worrying - the shadow bug might finally get fixed now, but what about any new bugs introduced or discovered in 2.5? Will the community have to spend another 6 months constantly trying to convince the beta testers and LM that the bug exists, before they will even look at it?

 

Part of the reason for using a sim that's in active development instead of the "frozen in time" FSX is that any issues discovered get resolved. If known bugs are actively being denied and simmers that report bugs are discredited ("It looks fine to me, there must be something wrong with your system or your P3D install"), we're better off sticking with FSX - it certainly has issues, but those are well known and documented, and workarounds exist.

 

Beta testers need to get much less defensive about P3D, too. Your job is not to market the simulator and show it in the best light possible. Your job is to discover issues and bugs, and make sure they get communicated clearly to the developers at LM as well as the community (so we don't have to waste time troubleshooting our systems for issues that exist in the sim itself). You are allowed to give criticism and even to get annoying with the developers if you feel like they aren't paying attention.

 

Part of the reason for using a sim that's in active development instead of the "frozen in time" FSX is that any issues discovered get resolved.

 

A very good point, Jimmi. I wonder if the "vertical contrails" issue has been resolved in v2.5? Am I right in thinking that this bug appeared during the update from 2.3 to 2.4?

This attitude is worrying - the shadow bug might finally get fixed now, but what about any new bugs introduced or discovered in 2.5? Will the community have to spend another 6 months constantly trying to convince the beta testers and LM that the bug exists, before they will even look at it?

 

I've got to the point where I've decided I'm wasting way too much time trying to tweak and upgrade this buggy piece of software so it's going on the backburner for now until Lockheed Martin fix all outstanding issues.

 

Back to FSX DX10! I'll miss the cloud shadows. And that's about it. 

This attitude is worrying - the shadow bug might finally get fixed now, but what about any new bugs introduced or discovered in 2.5? Will the community have to spend another 6 months constantly trying to convince the beta testers and LM that the bug exists, before they will even look at it?

 

Part of the reason for using a sim that's in active development instead of the "frozen in time" FSX is that any issues discovered get resolved. If known bugs are actively being denied and simmers that report bugs are discredited ("It looks fine to me, there must be something wrong with your system or your P3D install"), we're better off sticking with FSX - it certainly has issues, but those are well known and documented, and workarounds exist.

 

Beta testers need to get much less defensive about P3D, too. Your job is not to market the simulator and show it in the best light possible. Your job is to discover issues and bugs, and make sure they get communicated clearly to the developers at LM as well as the community (so we don't have to waste time troubleshooting our systems for issues that exist in the sim itself). You are allowed to give criticism and even to get annoying with the developers if you feel like they aren't paying attention.

You make a very good point Jimmi. No news BTW on the flashing vertical lines when the building autogen slider is full right. The issue was acknowledged by Zach June last (problem withe autogen building batch processing if I understand well)  and ithey are seen by many users (apparently not by the B testers though  ) .

Wow, whats going on here?

 

Seems everytime an update is announced, people start to get freaking out! Does anyone remeber the last time as Rob was heavily attacked ("frame-discussion" as far as I remember)

 

 

We have two simulators here:

One, which is currently developed out of a really old piece of software.

And one, which is not developed and sticks as a really old piece of software.

 

 

 

It's up to each user which version he prefers

But stop nagging on the devlopers or testers as LM has clearly other development targets as we hobby flyers have. That just have to be accepted and one has to be satisfied with what we have now.

OMG!!!   :o Don't work!!! :Black Eye: They Broke it!! vertical whirly-do's are in the wrong folder...ORBX is in crisis!!   

TrafficPilot is giving up and going back to DX10 voodo land. Trolls and vultures are over head....OH wait a minute....Fox News Alert!! {key the music} Prepar3D 2.5 has not been released and is still in early Beta. Leaders from around the world as well as the flight sim community are asking folks to get a grip!!! Good God Almighty!!

 

 

Beta testers need to get much less defensive about P3D, too. Your job is not to market the simulator and show it in the best light possible. Your job is to discover issues and bugs, and make sure they get communicated clearly to the developers at LM as well as the community (so we don't have to waste time troubleshooting our systems for issues that exist in the sim itself). You are allowed to give criticism and even to get annoying with the developers if you feel like they aren't paying attention.

You should be one! Did you ask and offer LM your quality work or is it only talk where you're top?

Spirit

Rob, 

 

are the default clouds also white in the middle of the night? 

 

Suggest you watch the video I posted earlier in this thread ... start at 12:07 min mark ... you'll see difference between dusk clouds and midnight clouds when there is a slight moon.  The clouds look perfect at night to me ... but I'm sure opinions will diverge as they always do.

 

 

 

Your job is not to market the simulator and show it in the best light possible. Your job is to discover issues and bugs, and make sure they get communicated clearly to the developers at LM as well as the community (so we don't have to waste time troubleshooting our systems for issues that exist in the sim itself).

 

You need to be a little more passive/aggressive ... thanks for pointing out "my job".  You really want on the Beta team don't you?

 

Sorry JimmiG, but I'm going to have to shatter your fantasy world:

 

1.  How do you know these issues weren't reported?

2.  I have a job and it's not with LM.

3.  What have you contributed other than attacking the Beta process?

4.  Possible bugs need to have a process of replication, repeatable and consistent and specific details passed along to that end,  not "look terrain shadows don't work right".

5.  3rd party products often don't work or partially work with new Beta releases, so how exactly can they be "fully" tested?

6.  Many "bugs" being reported are often end user errors, 3rd party errors, and even nVidia driver errors.

7.  Have you calculated the shear volume of possible combinations of settings in P3D and then figure how you can repeat these tests between each Beta and RC released (often a few days apart)?

 

Frankly, your continued attacks on the Beta process are getting old, inaccurate, unrealistic, and uninformed.  Others (I believe Word Not Allowed) gave up on beta testing because he wasn't getting the responses he wanted ... you think any of us have some magical powers to prioritize LM's work efforts?  Refer to item #1.  If so, please do share this pixie dust with us.

 

Now, best beta contributions are those that don't come with EXPECTATIONS ... because those expectations are irrelevant to the process.

 

Cheers, Rob.

JimmyG...I will be happy to help pay for a version of X-Plane for you. I only ask in return that you never post on AVSIM again. You offer nothing but insults to folks like Rob who are doing nothing more than helping us enjoy our past time more. You sir are really offensive.

JimmyG...I will be happy to help pay for a version of X-Plane for you. I only ask in return that you never post on AVSIM again. You offer nothing but insults to folks like Rob who are doing nothing more than helping us enjoy our past time more. You sir are really offensive.

+1

Spirit

+1

Spirit

 

I suggest JiimyG starts is own software developing company and make his own flight simulator. I would than voluntary sign up for beta and complain about every little details.