December 30, 20169 yr ^ Yeah, whatever's wrong has nothing to do with the latest version of FSUIPC being compatible with the HF2, because it is. Yes, let's disregard everyone that fixes it by simply removing the fsuipc.dll. Clearly that's not the issue. Eric
December 31, 20169 yr Wrong. The manual says it pretty clearly: "26. Prepar3D version 3.4.18 is supported by this release." Interesting. As of right now, the FSUIPC website download description still says (in bold print): Prepar3D Versions up to 3.4 Hotfix 1 (3.4.14.18870). And it apparently does not work properly with HF2. I do note that the release of FSUIPC 4.959 predates the LM release of 3.4.18, and it doesn't specify a build number in the FSUIPC docs. I wonder if maybe LM made some last-minute changes to HF2 after Pete had finalized 4.959. For now it's a good thing not to be on the bleeding edge. P3D v3.3.5 with FSUIPC 4.955h, and Win 7 x64 with nvidia 368.81 drivers and a pair of 980Ti GPUs in SLI is humming along nice and stable without all the new OS/driver/P3D build issues. Regards Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
December 31, 20169 yr FSUIPC 4.959 is working properly on my Win7-64 Professional PC [GTX960/ Nvidia 376.33] with FSX Acceleration and P3D v3.4.18.19475 (HF2).RealAir Turbine DukeV2 , F1 GTN760 / PMDG737 Best Regards, Vaughan Martell PP-ASEL KDTW
December 31, 20169 yr Interesting. As of right now, the FSUIPC website download description still says (in bold print): Prepar3D Versions up to 3.4 Hotfix 1 (3.4.14.18870). And it apparently does not work properly with HF2. I do note that the release of FSUIPC 4.959 predates the LM release of 3.4.18, and it doesn't specify a build number in the FSUIPC docs. I wonder if maybe LM made some last-minute changes to HF2 after Pete had finalized 4.959. For now it's a good thing not to be on the bleeding edge. P3D v3.3.5 with FSUIPC 4.955h, and Win 7 x64 with nvidia 368.81 drivers and a pair of 980Ti GPUs in SLI is humming along nice and stable without all the new OS/driver/P3D build issues. Regards Well, I have zero problems with FSUIPC and P3D v3 and Hotfix 2. I am using it extensively for my controllers, FS Global Real Weather and the new AI Traffic limiter functionality. Might the problem be some addon that is dependent on FSUIPC that is incompatible with the latest FSUIPC version? This hobby sure makes you scratch your head until your hair falls off sometimes... Simmerhead - Making the virtual skies unsafe since 1987!
December 31, 20169 yr Zero problems with FSUIPC and P3D v3 and Hotfix 2 here, I am using ASN rather than AS16 though.
December 31, 20169 yr And the credit card(s). :wink: The $500.00 hammers just went up to $750.00. Nothing against LM they are a defense contractor you know. Best wishes BaldyB
January 1, 20179 yr Hey guys happy new year Question? Is it worth upgrding from 3.2 to 3.4? Running well here atm tho. Any advise is appreciated
January 3, 20179 yr Still unusable in SLI with hotfix 2, and has smoke effects flashing without it unless reverting back to older Nvidia driver. Hotfix 2 destroys P3D 3.4x in SLI.
January 3, 20179 yr Still unusable in SLI with hotfix 2, and has smoke effects flashing without it unless reverting back to older Nvidia driver. Hotfix 2 destroys P3D 3.4x in SLI. I have a clean Windows and P3D build. Before this I was having an SLI issue after installing Nvidia's latest. 2 GTX 780's, fyi. Everything is fine in the new build for me. Disclaimer: [email protected] on Asus Maximus X Formula, G.Skill TridentZ RGB 4x8GB 4266/17 XMP, EVGA 2080 ti Kingpin (8400/2160Mhz), Samsung 960 EVO 250GB PCIe M.2 NVMe SSD , 28TB HDD total - 4TB+ photoscenery, Romex Software PrimoCache RAM and SSD cache (must have!), 3x1080p 30" monitors, Samsung Odyssey VR HMD, Pimax 4k & BE HMDs, Samsung Gear VR '17, Homdio v1, Cardboard, custom loop 2x 360x64ML Rads, Thermaltake View 71, VRM watercool, Thermal Grizzly Conductonaut CPU (naked die), Fujipoly / ModRight Ultra Extreme System Builder Thermal Pad on MB VRM. 8x Corsair ML120 (slight positive pressure). 🙂
January 3, 20179 yr I have a clean Windows and P3D build. Before this I was having an SLI issue after installing Nvidia's latest. 2 GTX 780's, fyi. Everything is fine in the new build for me.Not sure I understand. What drivers are you using with your 780's in your new build? Mike
January 3, 20179 yr I have a clean Windows and P3D build. Before this I was having an SLI issue after installing Nvidia's latest. 2 GTX 780's, fyi. Everything is fine in the new build for me. That is really good news .... did you share with the P3D forum and here /: http://www.avsim.com/topic/500111-p3d-update-broke-working-sli/page-3 Best Regards, Vaughan Martell PP-ASEL KDTW
January 4, 20179 yr I have a clean Windows and P3D build. Before this I was having an SLI issue after installing Nvidia's latest. 2 GTX 780's, fyi. Everything is fine in the new build for me. Something nor right here. This is not what has been happening to those with SLI setups and following LM procedures. Hotfix2 was supposed to work with client change only on existing full P3D working program! You had to do a complete uninstall and then re-install including windows itself and then P3D 3.5 from complete scratch on top of that? Somethings are not right here. That is not the drill given by LM! Are things that bad that we have to do a reformat, load a new operating system, drivers, download software and hope for the best? LM has said nothing about something like that! What did you leave out if anything? Do you have all the usual addons, or more bare bones? FSUIPC?
January 4, 20179 yr Hey guys happy new year Question? Is it worth upgrding from 3.2 to 3.4? Running well here atm tho. Any advise is appreciated I upraded to 3.4 when it was first released and ran into more issues than I ever had with any previous version of any flight simulator. I then walked through fire both over at LM as well as in here to get back to 3.2. Now back on 3.2 I have zero issues. I haven't seen one single VAS issue despite using very complex add-ons such as the NGX, Orbx Global Vector, FlyTampa's latest EHAM scenery to mention just a few. And this is using mid to high settings both in P3D as well as for my add-ons. At this point I won't touch anything from LM until/if they release a 64-bit version and I'll hold off with that one too until the smoke has cleared. I prefer enjoying my products rather than spending my time troubleshooting and paying big money only to be a guinea Pig. So...by now you should have guessed my advice is stay with 3.2 and forget about 3.4 and enjoy your working sim instead.
January 4, 20179 yr Lets hope there is one more working hotfix for 3.4 or a new 3.5 (doubtful) that addresses the SLI and remaining problems, then leave things well enough alone except for ongoing support. As it is now, P3D v 3.4 with hotfixes is an unworkable and unusable platform for those customers who were encouraged and supported in SLI. We need help and a solution for our P3D SLI situation. Thank you.
Archived
This topic is now archived and is closed to further replies.