.

Got it...about to try it out for the first time!

Any noticeable difference regarding VC FPS?

Any noticeable difference regarding VC FPS?

According to the single forum message that's in at the moment, 1 user says there is...DJ

According to the single forum message that's in at the moment, 1 user says there is...DJ

Yeah, I just seen that post. Well, I'll see if there was an improvement in a few . Hopefully, there is.

I just completed a KBOS-KBWI flight with the SP and I did see some VC FPS improvement. I am now only loosing about 5 FPS with the mouse on vc.

I installed and loaded up a flight but my Go Flight MCP Pro is not working. Uninstalling the drivers and reinstalling in an effort to get it to work If I can't I will just fly the old fashioned way and I am going to fly KLAS-KSEA with ORBX scenery to see how she does. This has never been an issue for me except with autogen. I will try it with autogen and see how it works.

Any list of whats in the SP?

Any list of whats in the SP?

I second this. I haven't bought iFly's 737 so I'd like to know what progress they've made on it.

Any list of whats in the SP?

Fix List:Only the items listed are included, if an item you were concerned about is not mentioned then it is not included in the SP and will be added to the Feature Pack. Please do not post about any items not on this list, save those post for the development forum. 1. Update the MCP altitude acquisition/deviation alert logic. 1). Alt alert sound should have a 3sec delay(not 5 sec); 2). In level flight, the alert triggered is also the steady white acquisition alert and not the flashing amber deviation alert.2. Displays CMD as soon as the second AP is engaged. The CMD should display until the second autopilot really engages (below 1500ft AGL - appearance of FLARE armed in white)3. CDU CLR key can't be controlled by hotkey4. Re-check the VNAV logic.5. Sometimes, "LVL change 400fpm for short climb/descent" does not work.6. Use 3 seperate altimeters for captain/fo/standby panel. Add ALT DISAGREE alert, display when capt/fo altitude disagree more than 200ft and more than 5 second.7. Standby altimeter with altitude error.8. Clicking on 2500FT, 200FT or 20FT at SIMU Menu--Style page does not open the corresponding menu but redirects you to the previous option you opened.9. The cabin may still pressurizes even with both packs are all off10.If in vc mode and there is no tower view available and select tower view from fs menu, then back to vc mode, all screens will blank until press "F9" or use "S" to re-select vc.11.Two independent turnoff lights12.FMC does not calculate T/D if there is no runway in the route13.Update the APU FF logic.14.Add lights test switch15.If open simconnect log mode, there will be many exception error in log file.16.Update the model17.Add more options in the style menu.18. The strange characters on the N1 limit page are back, this occurs when i load the "normal" panel state.19. Spelling mistake on the lights test panel.20. No automatic auto-thrust reduction if automatic thrust reduction selected.21. IRS alignment time option works incorrectly.22. Brake temp sensor is not correctly modelled.23. If N1 set knob is not at AUTO mode, the N1 may excess the limit.24. Change the cabin altitude logic, if loss bleedair/pack, the system use about 1500~1800vs to loss pressure.25. Update the gear brake cooling rates26. Change the N1 limit logic. A) With AT ON, N1 will not exceed green N1 limit. :( With AT OFF and EEC in normal, N1 will not exceed amber N1 limit. C) With AT OFF and EEC in ALTN, N1 can exceed amber N1 limit. D) The manually set N1 value has no effect on AT operation27. GPWS provides height callouts based on the altitude set by the Captain's Minimums selector.28. Re-build the logic for A/T engage/disengage, during VNAV PTH 29. When FD takeoff mode and cross thrust reduction altitude, and with auto thrust reduction mode ON, the A/T should engaged from ARM to N1, while N1 switch at MCP not light up.30. DECEL point also available for way-point speed constraint.31. Modify Approach Logic32. Re-build G/A logic33. GPWS sensitivity readjustedVC Mouse IssueDespite support from other developers we have not been able to fix the VC Mouse issue. Using a external frame rate limiter does improve things on pc's with the issue but does not prevent it. We have managed to squeeze some more frame rates from the aircraft and the testers are seeing approximately 15% improvement. While this does not seem much on low spec systems it does make things visibly smoother which is the aim at the end of the day for the aircraft to run smoothly and not being fixated on frame rates. A good example of this was on my top machine the external model runs over 120FPS but that creates a stutter until you limit the frames. With the frame per second limited it then becomes smooth as silk.

I can also say that the VC FPS issue has improved. But better (not a lot) performance than before.

Any noticeable difference regarding VC FPS?

No difference here.

No difference here.

I've never had an issuevwith the VC fps before, but I can say that the sim seems smoother now after the sp. The flight model locks onto the ILS approach much better now too. I did note that the first time I tried it after installing the sp I could load one of my old panel states, however after that first time I got a CTD each time,.Bruce.

For the fps tweakers, there's an extra option in the iFly menu now to set up the refresh rate of the gauges. As this sort of option helps on many other planes when running on weaker systems, it's surely worth a try.Uploaded with ImageShack.us

I've taxied around a bit, on one engine, just to check if it's as hard or even impossible as on some of my other birds. You still need some rudder there, but you can taxi successfully so far, while most of my other aircraft ended up in 'turning static'.I'd still say that the FSX nosewheel needs more friction to come close to any rw operation since the yaw effect is quite prominent without this stabilizing force. But that's a layman's assumption of course.I'd like to read some reports about the new (gauge) performance options, I must admit.I didn't have any trouble with the pre-SP1 state, so I can hardly test if it really helps the folks actually having some fps problems.

Chris, tks for the list. I wonder why they havent mentioned the SP on their general forum.