[FX] bangbang023: 07-01-30 [Trunk/Win32](O2/GAL)


Recommended Posts

Feeling better?

Does today's include the print patch?

585395709[/snapback]

Yes, besides a cough, I'm good now. No, it doesn't include the print patch. For some unexplainable reason, it also broke something entirely different and I didn't want to risk functionality loss.

hey bangbang, why do you update daily?

585395930[/snapback]

um because there are daily updates.

hey bangbang, why do you update daily?

585395930[/snapback]

These are nightly builds in case you didn't know, not release builds. They are the very latest code and are not gauranteed to be stable, there are usually things broken.

These are nightly builds in case you didn't know, not release builds. They are the very latest code and are not gauranteed to be stable, there are usually things broken.

585398948[/snapback]

umm, that is incorrect. If firefox didn't make an "unstable" build, they wouldn't release it to the public without having it being tested first. Since there is nightly builds... they are stable, and whatever is tweaked, is tested before posting (Y). they have a full 24 hours to test it out before launching a nightly build.

Sorry man, but flightmike1 was right. The nightly builds are often plagued with severe issues, especially early on in a branch merging. They do not spend the entire 24 hours testing a build. They simply compile it and, if it completes, they upload it. They may smoke test them, to some degree, but I'm not 100% on that.

Well, BangBang, I haven't got the slightest idea what you're actually doing here but it seems you're making a significant contribution to the Neowin community so I want to thank you for that. Since I haven't heard of SSE2 I'm doubting my processor supports it (Athlon XP) but thanks all the same for doing whatever it is you're doing!

Thank you XenonicRob. Basically, I optimize the code base to run more quickly on systems that support the SSE2 instruction set. Your processor does not support it, unfortunately. While I don't contribute to the Fx world as many other do, I hope my builds so help out some people, at least.

While I don't contribute to the Fx world as many other do, I hope my builds so help out some people, at least.

585418609[/snapback]

Well if you say that, and you release build every day (apart from some off days) who does more then that?? lol :huh:

Well if you say that, and you release build every day (apart from some off days) who does more then that?? lol :huh:

585418846[/snapback]

Guys like mmoy or guys who submit patches that get used in the official code. I'm a builder, but the coders do a lot more work than I.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, unpacking and setting up the smart scope + tripod for equatorial tracking, mucking around with settings, maybe shoot some calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!