FSDreamTeam forum
General Category => General Discussion => Topic started by: Dimon on September 29, 2015, 02:28:50 pm
-
Folks,
Will the installers be V3-ready as of tomorrow? Can't wait to test VAS usage at CYVR.
Also, if you were part of beta-team, could you please comment on VAS savings over 2.5? Rob A. is claiming that those savings are close to 800MB-1GB and that's A LOT. We don't even need 64bit version in this case, I guess.
Thanks in advance
-
Yes, we still need a 64 bit version. May be better on VAS, but still has a 4 gig limit. I respect Rob A., but I'm skeptical of his 800mb-1gb assessment.
-
We will be able to make our own conclusions by the end of this week. I will keep both v2 and v3 and make tests with totally identical environment (scenery, planes, ai)
Sent from my iPhone using Tapatalk
-
Well, even if Rob's assessment is wrong by double, we'll still be in much, much better shape.
-
Yes, we still need a 64 bit version. May be better on VAS, but still has a 4 gig limit. I respect Rob A., but I'm skeptical of his 800mb-1gb assessment.
Even if this isn't 100% true, this makes me happy:
"Improved memory management reducing overall VAS usage and spikes"
"Unused terrain detail textures no longer loaded"
This could mean that you can now do longhauls and still be able to land at your destination without running into OOM.
-
Will the installers be V3-ready as of tomorrow?
The installers recognize V3 since several months by now...we only had to keep the Addon Manager .DLL updated for all the Beta builds, which we have been doing basically every weekend since July :)
Can't wait to test VAS usage at CYVR.
I made a quick test with KLAX:
P3D 2.5
http://update.fsdreamteam.com/images/fsdt_klax_P3D_2_5.jpg (http://update.fsdreamteam.com/images/fsdt_klax_P3D_2_5.jpg)
P3D 3.0
http://update.fsdreamteam.com/images/fsdt_klax_P3D_3_0.jpg (http://update.fsdreamteam.com/images/fsdt_klax_P3D_3_0.jpg)
And with FSX:SE as a comparison:
FSX:SE under DX9
http://update.fsdreamteam.com/images/fsdt_klax_FSX_SE_DX9.jpg (http://update.fsdreamteam.com/images/fsdt_klax_FSX_SE_DX9.jpg)
FSX:SE under DX10
http://update.fsdreamteam.com/images/fsdt_klax_FSX_SE_DX10.jpg (http://update.fsdreamteam.com/images/fsdt_klax_FSX_SE_DX10.jpg)
I tried to match P3D settings as close as possible. I loaded the default F-22, with no AI Traffic and no other 3rd party sceneries installed, but it's the same in both sims, so we are really interested in the differences under the same configuration.
And yes, there's some significant VAS optimization from P3D 2.5 to 3.0.
While FSX:SE (under DX10 only) is still A BIT better, I don't think it's a fair comparison, since the graphic quality in P3D is so much better, there are no proper shadows in FSX, weather is far less detailed, no cloud shadows, no HDR, Bloom is unusable because of the fps impact, etc.
-
Yep, ~600Mb between v2.5 and 3.0. That's truly nice number to read
Quick question - did the folders' structure change much?
-
That sounds really nice :) , but can we have the license active in both 2.5 and 3.0 at the same time to test the differents our selves ?
Thanks
Michael Moe
-
That sounds really nice :) , but can we have the license active in both 2.5 and 3.0 at the same time to test the differents our selves ?
You can install P3D 2.5 and 3.0 without any issues, but they are separate licenses.
-
Umberto, in order to switch from FSX to P3D v3 I would just like to know if I will be able to use Rome X scenery some way. Will I have to rely on a yet-to-come migration tool? Or do I have any hope to be already able to use it? Or will you make an installer for v3? Or can I roughly move the scenery files from my FSX folder to the P3D folder?
Thank you.
-
Umberto, in order to switch from FSX to P3D v3 I would just like to know if I will be able to use Rome X scenery some way
This is not supported for the time being. We might update the installer later on.
-
So you mean that for the moment there is no way of using Rome X in P3D?
-
So you mean that for the moment there is no way of using Rome X in P3D?
There might be a way, but it's not supported by us or by the installer.
As I've said, we might update the installer later on, but it's a matter of priorities, and you just can't expect a scenery made 8 years ago for FSX only, by another company, should be used "immediately", on a sim released YESTERDAY.
-
A very different question now.
Umberto, do you think Prepar3D v3 offers new ways for developer?
-
Umberto, do you think Prepar3D v3 offers new ways for developer?
P3D V2 already added A LOT of new features to developers (in fact, the biggest changes were from V1 to V2), and P3D V3 basically adds things related to the Avatar mode, the Speedtree library and the ability to create Gauges and scenery objects using Scaleform/Flash.
The real issue is that, as long as we need to support FSX too, which thanks to the Steam version is now available again to buy, it's way cheaper and more accessible, it's a very tough decision to spend valuable resources to do something that will work only with P3D, let alone only in P3D V3.
If we wanted to do something that really leveraged *everything* non-backward compatible that P3D has to offer, it's WAY more complex than it ever was when moving from FS9 to FSX. Especially for things like utilities or anything with some kind of behavior, like GSX or XPOI.
I guess we might try adding something simple first, that wouldn't require redoing the whole thing for FSX too.
-
Hi Virtuali,
I am bit confused. I own a lot of FSDT FSX products like KJFK, KDFW, KLAX, KIAH and GSX.
Can I safely move these products to P3D v3 folders (simply copying and pasting) without breaking anything or should I wait for future installers ?
Would there be any additional price cost attached to using the future installers ?
-
Can I safely move these products to P3D v3 folders (simply copying and pasting) without breaking anything or should I wait for future installers ?
You CANNOT "move" anything!! You must run the proper installers that, as I've said in this same post some messages before:
http://www.fsdreamteam.com/forum/index.php/topic,12555.msg95176.html#msg95176
The installers recognize V3 since several months by now
So yes, you need updated installers, and they are all already available now. Just download them and install into P3D V3 when asked. They are all totally free, of course...
-
Hi Virtuali,
I am bit confused. I own a lot of FSDT FSX products like KJFK, KDFW, KLAX, KIAH and GSX.
Can I safely move these products to P3D v3 folders (simply copying and pasting) without breaking anything or should I wait for future installers ?
Would there be any additional price cost attached to using the future installers ?
I just "ran" the new installers directly from this site and all the airports loaded fine. In fact, I didn't even have to re-enter my product keys.....the airports were active. Works great in P3D V3.
Thank you Umberto.
Bobby
-
Umberto, you are the one knowing this.
There is a "rumor" around saying we shouldn't install sceneries (airports and stuff) into the root folder of Prepar3D v3 because of the updates LM offers in the future.
Is this true, or can we continue install sceneries and stuff like we did in v2.5?
-
There is a "rumor" around saying we shouldn't install sceneries (airports and stuff) into the root folder of Prepar3D v3 because of the updates LM offers in the future.
During the Beta period, I always updated P3D using the new system of updating just the client, instead of reinstalling everything ( which means just 100MB to download instead of 10GB ), and there weren't any problems with any of our products.
Yes, the general principle of developer not having to change "core" files, sounds reasonable, except it cannot always be applied in real world. What about, for example, if a core P3D file file MUST be changed, otherwise the addon product would have issues ?
Let's the take default Pushback truck, that we must remove when installing GSX (otherwise there will be two trucks, possibly on top of each other, wasting VAS and fps...). Since there's no way to disable *only* that vehicle, without disabling the whole Scenery\Global\Scenery in the scenery.cfg and thus killing most of the default airport objects, we don't have any other choice than patching the .BGL to remove *just* the default pushback truck, leaving all the rest intact.
This was just the first example that came to my mind, but I'm sure there are plenty, considering how many 3rd party addons are out there.
Even LM has admitted that some addons (such as OrbX) MUST be installed in the root folder, otherwise they won't work, but I'm sure they are not the only ones.
Yes, I agree the new structure has some merit, but it's just a suggestion, because some changes might be reverted by LM updates but, at least as far our products are concerned, the worse you'll have to do is that you will have to relaunch our installers, in case this will ever happen.
Which, at least in our case, will not have any impact on the product activation, since we never stored such information in the root of the sim, and not even as files, but they are safe in the registry in their own section, separated from the section used by the sim itself, allowing to uninstall/reinstall our products (and even the host sim) an unlimited number of times, without worrying about activation.
Is this true, or can we continue install sceneries and stuff like we did in v2.5?
I cannot comment on any scenery or product out there, but you can surely continue to install FSDT products using their current installers, which works in P3D V3, and trust the installers and the uninstallers will do their job correctly.
-
Is GSX supported yet in v3? Only I just re-downloaded the latest installer from the website and although the button says FSX / P3D the only installer is the FSX one which only installs to FSX/FSX:SE.
Many thanks and keep up the good work
-
Is GSX supported yet in v3?
Reading this thread would have provided you with the answer.
the only installer is the FSX one which only installs to FSX/FSX:SE.
Have you TRIED the installer, or you assume it will "only installs into FSX", just because it's CALLED gsx_fsx_setup.exe ? It has always been called like that since the first P3D v1.x was released, years ago.
-
Yes, we still need a 64 bit version. May be better on VAS, but still has a 4 gig limit. I respect Rob A., but I'm skeptical of his 800mb-1gb assessment.
Am wondering why you say need a 64 bit version as they have not gone to 64 and now that V3 is out and is Vas friendly would not expect to see it for sometime.
-
Well, there's the danger that, should a 64 bit version would eventually come out in the future, developers won't restrain themselves anymore, and they might be feel entitled to waste GB of data with no regard of optimization whatsoever "because it's 64 bit".
The end result will be the sim won't crash for exhausting VAS anymore, but it will be slow as hell...I'm playing Galactic Civilizations 3 right now, which is ONLY 64 bit, and sure it doesn't crash, but sometimes (when the game has progressed for a while and you have hundreds of planets active) you must wait one minute or more for your next turn. But it never crashes...
-
Hello FSDT Team,
Just to say thanks for quick update for P3D. Downloading all sceneries again for my V3. Its a shame that many of the most important developers still delay their updates, but glad to see you are among the little risponsible to go ahead for your clients... ;)
A little comment: May be its a good idea to put kind of sticky thread above for quick refference regarding the V3...
8)