Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

23SEP11 Update: SP1, Hotfixes and the 6700

Featured Replies

A lot to look forward to ! Thanks PMDG !! Fred.

Frederic Steiner.

B7382.jpg

  • Replies 100
  • Views 30.2k
  • Created
  • Last Reply

Top Posters In This Topic

This "trend" has been the the norm for a very long time for complex multi-feature s/w products. I recall moving to this model late 90's. We "rolled out" features on a regular "milestone" scheduled basis. At each planned milestone, the product was evaluated and released based on the maturity (feature and regression testing state) of the build. Those features that were not "hardened" were not integrated in the scheduled release and had to wait until the next scheduled "rev" milestone. Without using this model, customer's would have to wait years before for a final product hit the market. While it seems that pmdg are somewhat sheltered by being having a lock on premium fsx addons and might enjoy the luxury of not having to cover a full payroll based on the revenue generated by these products (purely speculative), there are great advantages to using the phased incremental rollout model. Other than the obvious (not waiting for 3 years per product), one of these advantages is the exposure of less code to more users in a gradual way. This effectively widens the "beta" spectrum and allows early discovery of larger problems. It potentially shortens the response time to serious bugs since the lines of code delta is smaller and partitioned into distinct functional areas. This also, by definition reduces the total number of bugs per release cycle thereby increasing the customer's perception of quality. I am very sure that the "area under the curve" since the Aug 4 release date would have been much smaller had this approach been adopted. IMHO (and in the grand scheme of things totally irrelevant), the ngx would have benefited greatly using this approach. A practical example of this might have been rolling out the ngx much much earlier with less features along with a scheduled list of added features to be rolled out in time (no dates, just the planned sequence of features). I am quite sure that the majority of customers would have rather had the ngx earlier with less. Example might be the HGS, the crazy (in a positive sense) number of aircraft options, cabin pressure/temperature, brake pads choices, certain obscure fmc extras etc. The point is that the ngx would ultimately evolve into its final wonderful state but in an evolutionary sense with much less "gnashing of teeth"/"churn". In my view, Ryan is completely correct. The NGX should have many many many smaller less impact REGULAR updates and the above mentioned feature roll out. Ideally, a "check for updates" feature would be available from within FSX (from the addons->pmdg menu). If not technically possible due to fsx limitations then as part of a stand alone program such as the livery/textures program. No muss no fuss just regular slow but steady progress. ( A side benefit would be the reduction of the forum "noise" on the topic of release and hopefully more focus on the actual flying of the NGX). The above "arm-chair-quarterbacking" was simply a single voice from the sea of customers and was written in the most positive and constructive spirit. I have had the NGX installed and have been flying since the release date Aug 4 without a single major problem. This is a more than a great aircraft and I am very grateful for the dedication and technical abilities of the PMDG team. It has no doubt brought a ton of enjoyment to many and will keep doing so for many many years. As my sig says, Thanks PMDG!
+100 One of the best written and technically relevant posts I have yet seen on this forum, and well worth QUOTING.

however, i guess this thread is not meant to be open and all posts will be removed anyway to announce the fixes that are going to be published today in order to not open another thread.

Tebin Ulrich

How long it takes to orbit the sun in America around the earth?Where is the hotfix for now, Robert?We want to fly our aircraft!

Stephan

Banner_MJC1.png

How long it takes to orbit the sun in America around the earth? Where is the hotfix for now, Robert?We want to fly our aircraft!
It's not even noon there (Pacific Daylight Time) . Plenty of Saturday left.
avsimsig.jpg

Good to hear this - thanks PMDG.Looking forward to flying UK to (possibly Rhodes) and return in the next few days. Regards, Carl Beeby

Carl Beeby

How long it takes to orbit the sun in America around the earth? Where is the hotfix for now, Robert?We want to fly our aircraft!
BushPilot2 --- Just wait man !! --You, of all people should realize that "A bird in the hand, is worth two in the bush" LMAO.gif

Is the SDK going to be released to developers with SP1??

John C

Both "OFFICIAL" PMDG 4096, 2048 & 1024 texture files, as well as 4096,2048 & 1024 textured models. While users are able to resize the Texture files for added performance, they were not able to modify the textures within the model files.
I'm a bit lost here - what would need be changed to the model if textures are sized down? Don't they work out of the box? When I resized them they worked pretty well. I'm probably missing something here though.
Other than the obvious (not waiting for 3 years per product), one of these advantages is the exposure of less code to more users in a gradual way. This effectively widens the "beta" spectrum and allows early discovery of larger problems. It potentially shortens the response time to serious bugs since the lines of code delta is smaller and partitioned into distinct functional areas. This also, by definition reduces the total number of bugs per release cycle thereby increasing the customer's perception of quality. I am very sure that the "area under the curve" since the Aug 4 release date would have been much smaller had this approach been adopted. IMHO (and in the grand scheme of things totally irrelevant), the ngx would have benefited greatly using this approach.
+10100...
The above "arm-chair-quarterbacking" was simply a single voice from the sea of customers and was written in the most positive and constructive spirit. I have had the NGX installed and have been flying since the release date Aug 4
Again, +1. Well said. I was always thinking it could have needed more testing (and I also meant to say 'by more people', and I did not mean to get included in any way!) before release, but you found way better words for it so in fact I said nothing. Big%20Grin.gifsig.gif
+100 One of the best written and technically relevant posts I have yet seen on this forum, and well worth QUOTING.
I spent many years leading commercial software development in the financial arena and we moved from the old 'waterfall' methodology to 'Agile' to allow us to release the software and produce 'sprint' releases every few weeks or month with bug fixes and incremental product enhancements. Worked nicely for the most part. Joe

Joe Porter

ngxu_banner.png

Banner_FS2Crew_Beta_Tester.jpg

Can't wait!

Ken Ehlers
F70

Boeing777_Banner_Pilot.jpg

I'm a bit lost here - what would need be changed to the model if textures are sized down? Don't they work out of the box? When I resized them they worked pretty well. I'm probably missing something here though. sig.gif
My mistake -- I was getting mixed up with the Guage Graphics that are in the Gauge dll, and not in the Model, although Ryan did mention the models having something to do with the Texture Resolution applet. GOOD CATCH !!!

im agreed...............relax boys.

ATO VATMEX director, VATNA P1-P2 instructor (spanish), VATSIM 897455, more than 9000 hrs flight.
 

 

 

 

Both of those things will come in SP2 (or whatever we end up calling it now) - we'd originally planned on doing them for SP1 but the fixes for stuff had to take precedence for SP1. He didn't mean they're "new" in the sense of looking different, they just have fixes to various issues that were found between release and now. 2D throttle panel - probably not, sorry. It's a significant amount of extra work to make animated throttles in 2D and we think the time is better spent on other things. Flashing cursor is an FSX thing - I do not see that myself with the NGX, but I have seen it with other aircraft non-PMDG. Nothing we can do about it, it's not a code issue. The 600/700 is not free - SP1 is. SP1 is required to use the 600/700 though. Aircraft.cfg file in each variant folder - build 2292 is the latest. Relax guys - this isn't something inside the airplane, it's an external app that switches texture size. (ie 4096 vs 2048 vs 1024) It's direct swapping out of texture and model files, not some complicated thing in real time inside the sim...
Ryan for clarity, is this hot fix well see today now kind of sp1 with sp2 being the sp we were originally expecting yesterday but estimated for 1oct....so around the 1st we will see the sdk, or is that at a later further date?

Regards

 

James Carr

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.