inconsistency
Results 1 to 17 of 17

Thread: inconsistency

  1. #1

    inconsistency

    Let me say that I find this subgroup quite inconsistent. There is a fundamental difference between versions 1 to 3 and version 4: the PBR. I do not see the usefulness. It would have been better to separate the 32 and 64 bit versions than this operation which does not meet any criteria satisfying from a technical point of view! So its attendance seems confidential.

    Really weird ...

    JMC

  2. #2
    Quote Originally Posted by gastonj View Post
    Let me say that I find this subgroup quite inconsistent. There is a fundamental difference between versions 1 to 3 and version 4: the PBR. I do not see the usefulness. It would have been better to separate the 32 and 64 bit versions than this operation which does not meet any criteria satisfying from a technical point of view! So its attendance seems confidential.

    Really weird ...

    JMC
    I said the same thing the day after the breakup. 32-bit vs 64-bit should have been the cutoff.

  3. #3
    Quote Originally Posted by gastonj View Post
    Let me say that I find this subgroup quite inconsistent. There is a fundamental difference between versions 1 to 3 and version 4: the PBR. I do not see the usefulness. It would have been better to separate the 32 and 64 bit versions than this operation which does not meet any criteria satisfying from a technical point of view! So its attendance seems confidential.

    Really weird ...

    JMC
    Agree 150%!

    Priller

  4. #4
    I'll see what can be done.
    Watch this space.
    "Illegitimum non carborundum".

  5. #5
    +1 agree!!
    Flavio - P3D v4.5 HF3 - Win 10 Pro 64
    i74960X 4.5ghz - ASUS Rampage IV Black Ed. - Corsair H150i - 32gb Ripjaws Z - ASUS RTX2080 Super - ASUS 27'' MG278Q 2k 144mhz - SSD 960Gb + 480Gb Hyper X 3K

  6. #6
    Could not agree more!
    Well I've been to one World Fair a picnic and a rodeo and that's the stupidest thing I've ever heard come over a set of earphones.

  7. #7
    I agree also.
    +1
    Joe Cusick
    San Francisco Bay Area, California.

    I am serious, and stop calling me Shirley.

  8. #8
    Quote Originally Posted by wombat666 View Post
    I'll see what can be done.
    Watch this space.
    Thanks for quoting Rachel Maddow Wombat!

    We're watching!!

    Priller

  9. #9
    Under consideration, positive reactions from the Admins to date, still a couple to come onboard yet.
    Patience is a virtue.
    "Illegitimum non carborundum".

  10. #10
    Quote Originally Posted by wombat666 View Post
    Under consideration, positive reactions from the Admins to date, still a couple to come onboard yet.
    Patience is a virtue.
    Not sure if it is a possibility with the forum software but I also belong to a motorcycle forum where we can add a prefix for which state we're in ( QLd is even maroon! ) . It puts these little boxes with QLD in it before the thread title. The primary issue in splitting it 32 bit V 64 bit is that V5 is different to v4.5 as is PBR for each as well. There may still be a need to de-lineate between versions.

    Anyway big thanks to the poor fella/fella-ette that has to do the change over... that is some serious behind the scenes stuff to do!

  11. #11
    Quote Originally Posted by pilto von pilto View Post
    Not sure if it is a possibility with the forum software but I also belong to a motorcycle forum where we can add a prefix for which state we're in ( QLd is even maroon! ) . It puts these little boxes with QLD in it before the thread title. The primary issue in splitting it 32 bit V 64 bit is that V5 is different to v4.5 as is PBR for each as well. There may still be a need to de-lineate between versions.

    Anyway big thanks to the poor fella/fella-ette that has to do the change over... that is some serious behind the scenes stuff to do!
    v4/v5 are both 64-bit and PBR.

    v1/v2/v3 were all 32-bit and PBR wasn't even a thing for P3D back then.

    That's the logical cutoff.

  12. #12
    Just my two bits here but...

    Recognizing that there is a ton of work involved re-tasking forums and the like, I think it may become evident very quickly that V5 is an entirely different animal all together. Whereas V4 went 64bit PBR, it was still a bit entry level for devs wanting to move in that direction.

    From a design standpoint V5 PBR is so different than anything that went before, it actually requires a complete re-think of the rendering mechanics of the simulator. The art is completely different, the engine does a tremendous amount of the work we used to bake in, and much more.

    I agree a separation between Versions 1-3 and the 64 bit cousins is necessary. That agreed upon, in my opinion V5 represents such a major break away from any of the predecessors, it might possibly be appropriate to view it as an entirely separate category.

    Just my opinion, but something to consider.
    He who knows nothing is closer to the truth than he whose mind is filled with falsehoods and errors.
    Thomas Jefferson

    Intel Core i9-9900K Coffee Lake | Cooler MasterAir Maker 8 CPU Thermal Cooler | ASUS ROG Strix Z390-E LGA 1151 | CORSAIR Vengeance RGB Pro 32GB 288-Pin DDR4/3200 | EVGA GeForce GTX 1080 Ti 11GB | SAMSUNG 860 EVO Series M.2 1TB SSD | Mushkin Chronos 240GB 2.5 SSD | WD Black 2TB 7200 RPM |WD Black 5TB 7200 RPM | CORSAIR HX Series HX1200 PSU | Windows 10 HP 64-bit

  13. #13
    What should we think, that apart from P3DV5, nothing is worth looking into and putting P3D V4.5 away ?
    JMC

  14. #14
    Quote Originally Posted by fsafranek View Post
    v4/v5 are both 64-bit and PBR.

    v1/v2/v3 were all 32-bit and PBR wasn't even a thing for P3D back then.

    That's the logical cutoff.
    Ahh sorry I'm going to have to semi - disagree. The PBR and gauge and code changes between 4.5 and 5.0 are such that there is a need to have a difference. From a developers point of view. and that is the key.

    Is SOH an end user only forum where support isnt required by devs or questions being answered by other end users ? Then agree your cut off makes sense.

    However if you get the... "CE westland lysander gauges not showing up in P3d PBR" thread then is that 4.5 pbr or 5.0 pbr? Is that 4.5 Gauge coding or 5.0 gauge coding? Is that 4.5 export or 5.0 export ? Which version of simconnect is being used? ETC. But again that is from a dev/end user support side.

    A combined P3d forum with tags could work .

    [p3d v2.5 ] title of thread
    [P3d v5.0 ] title of thread
    [P3d v4.5 ] title of thread.

    However that poor admin...

    GastonJ : I still run 4.5 over 5.0 all the time. It doesnt crash it looks better and is quicker to develop in. I do wonder how many people are using v1 - 3 however. I think I've had one email about 2.5 support in the last 2 years.

  15. #15
    Hello,

    I think a combined P3D forum would be the best choice. I agree with you!
    But it seems to me that the majority of the posts to this forum are "end user", "advertisement/discussions" of commercial and free products. Maybe I am wrong!

    JMC

  16. #16
    All points are valid. Just to repeat mine with a little more backup.

    Although this is primarily an end-user forum many end-users are also pseudo developers, aka modders.
    And this is their home website so discussion and updates on a mod project tend to all take place here.
    Also many developers use it as free advertising of upcoming projects as they reveal the progress in hopes
    of generating pre-sale interest or when seeking assistance (information, opinions, suggestions, beta testers, etc.)
    from the forum members.

    There are already 51 pages of discussion in the new three-month old "v5" section with the oldest talking
    about v4 scenery compatibility. There are 71 pages in the nine-year old "Prepar3D V1-4" titled section.
    Seems like it would be easier to simply change the name of the earlier section to "Prepar3D V1-3" and be done with it.

    There is bound to be some overlap but it will eventually fall back so that it doesn't matter. And if people
    can be bothered enough to use the forum search feature they should be able to find what they need.
    Or start a new thread in the appropriate section.

    The longer it takes for some resolution the less likely there is to be any. Maybe that is the plan?

  17. #17
    Quote Originally Posted by gman5250 View Post
    Just my two bits here but...

    Recognizing that there is a ton of work involved re-tasking forums and the like, I think it may become evident very quickly that V5 is an entirely different animal all together. Whereas V4 went 64bit PBR, it was still a bit entry level for devs wanting to move in that direction.

    From a design standpoint V5 PBR is so different than anything that went before, it actually requires a complete re-think of the rendering mechanics of the simulator. The art is completely different, the engine does a tremendous amount of the work we used to bake in, and much more.

    I agree a separation between Versions 1-3 and the 64 bit cousins is necessary. That agreed upon, in my opinion V5 represents such a major break away from any of the predecessors, it might possibly be appropriate to view it as an entirely separate category.

    Just my opinion, but something to consider.
    The work isn't that huge really. Especially since the Prepar3D boards aren't that populated yet (compared to FS9 and FSX) Every IT guy with some knowledge of scripting could do the work in a working day. And that is taking things with a huge margin.

    How about one big Prepar3D board with three sub boards:

    v1-v3
    v4.x
    v5.x

    Priller
    Intel i7 9700K
    be quiet! Dark Rock 4 Pro cooler
    32 GB DDR4 Vengeance RAM
    Asus ROG STRIX Z390-E Motherboard
    Asus RTX 2080 Super ROG STRIX Graphics Card
    Samsung 1TB 970 EVO PCIe M.2 C: drive
    Western Digital 2TB WD Black Data drive
    be quiet! Straight Power CM1000W PSU

Members who have read this thread: 146

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •