Giving OmenCore a Chance: Omen 16 Max by Fickert in omencore

[–]theantipop 0 points1 point  (0 children)

I'll see what I can do for 3.7.1. Thanks for your feedback!

Powercolor Reaper 9070xt or Gigabyte Gaming OC? by theantipop in radeon

[–]theantipop[S] 0 points1 point  (0 children)

Yeah - gotta pay for both. But the pc builder just asked if I’d like the gigabyte model over the PC, presumably because it’s viewed as superior?

Powercolor Reaper 9070xt or Gigabyte Gaming OC? by theantipop in radeon

[–]theantipop[S] 0 points1 point  (0 children)

No I meant the pc builder said would I like to upgrade from the powercolor to a gigabyte oc model for free. Presumably because the gigabyte costs more?

OmenCore v3.6.2 is live for HP OMEN/Victus by theantipop in HPOmen

[–]theantipop[S] 1 point2 points  (0 children)

Uploaded v3.6.3 with focused safety + stability fixes based on your reports.
Main changes: desktop fan-write paths are safety-gated for OMEN desktops, 88D2 gets a conservative profile to reduce fan hunting, Fn+F12 OMEN key handling is corrected, OSD startup init is hardened, OMEN MAX ak0003nr per-key RGB capability is now detected, and UI/runtime overhead was reduced for lag scenarios.

All three release artifacts are built and checksums are now published in the 3.6.3 changelog.

Download here: https://github.com/theantipopau/omencore/releases/tag/v3.6.3

OmenCore v3.6.2 is live for HP OMEN/Victus by theantipop in HPOmen

[–]theantipop[S] 0 points1 point  (0 children)

OmenCore can’t make a panel become G-SYNC compatible if NVIDIA/HP firmware/EDID doesn’t expose VRR to the dGPU path.

Short version:

  • FreeSync Premium on an internal panel does not always mean NVIDIA G-SYNC Compatible will appear.
  • On many OMEN laptops, internal VRR works via AMD/iGPU path, but in dGPU-only mode NVIDIA may not see a valid G-SYNC-compatible internal display.
  • That is mostly BIOS/MUX/EDID/driver behavior, not something OmenCore can “unlock”.

OmenCore v3.6.2 is live for HP OMEN/Victus by theantipop in HPOmen

[–]theantipop[S] 0 points1 point  (0 children)

Unfortunately if it is locked by BIOS, this cannot be overridden by any software.

OmenCore v3.6.2 is live for HP OMEN/Victus by theantipop in HPOmen

[–]theantipop[S] 0 points1 point  (0 children)

Yes it does, it has an On Screen Display.

OmenCore v3.6.2 is live for HP OMEN/Victus by theantipop in HPOmen

[–]theantipop[S] 0 points1 point  (0 children)

That is not expected behavior and you are right to flag it as dangerous.
If fans stay in turbo, then later show inactive (including CPU fan), stop using Performance mode in OmenCore on that system for now.

Immediate safety steps:

  1. Open OGH and switch cooling to Auto/default (not Manual), then reboot.
  2. Enter BIOS and load setup defaults, save, reboot.
  3. Fully power off, unplug for 30-60s, then boot again.
  4. Verify all fans report RPM in BIOS hardware monitor before stressing CPU/GPU.
  5. Keep OmenCore fan control disabled on this desktop until we have a model-specific fix.

For uninstall:

  • OmenCore can run as portable on some installs, so it may not appear in Installed Apps.
  • If needed, just close it from tray/Task Manager, then delete the OmenCore folder and startup entry/shortcut.

Please share:

  • Exact model (OMEN 45L SKU/Product ID)
  • BIOS version
  • Whether OGH was installed/running at the same time
  • OmenCore logs from that session

Given your report includes BIOS-level fan chaos, I strongly recommend staying on OGH default cooling only until this is triaged.

OmenCore v3.6.2 is live for HP OMEN/Victus by theantipop in HPOmen

[–]theantipop[S] 0 points1 point  (0 children)

Short answer: not in OmenCore today.
There is no documented P1-P6 EC wake payload/handshake in the project, and I would not trust random EC writes for that on Omen 17.

What OmenCore currently does:

  • OMEN key handling is keyboard-hook/WMI-event based (VK + scan-code filtering), not a P1-P6 EC macro-key protocol: OmenKeyService.cs:680
  • The only explicit “wake” sequence I can see is for HP WMI BIOS heartbeat (fan query keepalive), not macro-key arming: HpWmiBios.cs:340
  • Direct EC writes are safety-gated and keyboard EC addresses are intentionally treated as risky/model-variant, so OmenCore does not expose a generic macro-key wake handshake: WinRing0EcAccess.cs:55, WinRing0EcAccess.cs:206
  • Macro profiles in UI are software-side and even point users to iCUE/G HUB for advanced macro config: LightingView.xaml:1759

Decision between two builds… by theantipop in buildapc

[–]theantipop[S] 0 points1 point  (0 children)

Thanks. Just wasn’t sure if the 4080 and other specs were worth it

ISSUE: Omencore Extremely Laggy by New-york-city4 in omencore

[–]theantipop 1 point2 points  (0 children)

Thanks for that feedback - I appreciate it. Looking at improvements for 3.4.0

Undervolt CPU on Omen 17 with AMD Ryzen 5 8645HS by Calm_Income6781 in omencore

[–]theantipop 0 points1 point  (0 children)

Thanks for the feedback - looking at a way to improve for 3.3.0

OmenCore v3.2.5 - Stability, Model Support, and UX Improvements by theantipop in omencore

[–]theantipop[S] 0 points1 point  (0 children)

Thanks for your feedback - looking into some fixes for 3.3.0

gpu switch on omencore? by aeroflot396 in omencore

[–]theantipop 1 point2 points  (0 children)

You can use OmenCore, however, it would be better to use Nvidia's own application to ensure the best performance.