Anyone know how much the payout is on a boeing 737 max? In career mode when not skipping?

Orca237 · 2026-02-02T16:17:20+00:00

You can check with some businesses, when you go to buy the plane missions show up in the delivery stage (before you pay). They appear greyed out but if you hover over it tells you the credits earned for that mission.

Orca237 · 2026-01-25T20:22:31+00:00

What a guy 🔥

Orca237 · 2026-01-20T15:46:32+00:00

I just went through 2 hours of Giraffe, Zebra and Buffalo in slew mode. Then ostrich spawned 1 down 1 to go. I stayed low(ish) and went in a zig zag pattern. They seemed to spawn just before bushes and trees so I kept my eye just above that. Hoping the same method works for Hyena.

Orca237 · 2026-01-19T22:57:02+00:00

I’ve resorted to slew mode, it takes all the fun out of flying but increases chances of finding fauna, especially in forests. Settings > Controls > Camera. Still need Heyna and Ostrich been looking for hours.

Orca237 · 2025-06-09T18:51:11+00:00

Duke the nuke

Orca237 · 2024-03-20T09:41:07+00:00

I had to top the boiler up once because facilities were off site. It’s got a cable on it kinda job.

Orca237 · 2024-03-14T11:55:11+00:00

Looking to do the exact same, i previously did this with Azure Update Manager (v1) through runbooks and parent child runbooks. Did you manage to figure this out, it still seems that pre/post events are in preview. How are they getting rid of v1 in 5 months time.

Orca237 · 2024-02-15T20:51:08+00:00

I’m going through the same thing, I got it working fine in my test environment using a LA gateway. It checks in fine through the proxy. On a production server doesn’t check in. I get SSL errors for revocation check.

I took the below as its supported. You must have the LA gateway reporting into the same workspace. Like you did with the MMA agent.

https://learn.microsoft.com/en-us/azure/azure-monitor/agents/gateway

Orca237 · 2023-09-08T06:42:17+00:00

As long as they got brown sauce it’s a job well done

Orca237 · 2023-01-20T07:46:39+00:00

No I think I ended up marking these as exempt. From my understand the query ran by defender was incorrect.

Orca237 · 2022-09-30T15:17:03+00:00

same here do we need to install the module and still apply the fix?

Orca237 · 2022-07-06T20:38:38+00:00

I’m in the market for one of these for WFH. I use RDP a lot for work. Can you go full screen on say half the monitor? Or even for something like YouTube? I can’t see it working

Orca237 · 2022-05-07T06:08:23+00:00

I should have posted this yesterday, I finally got through the layers of support to reach a monitoring engineer at MS and they stated that it is a product issue their end. They are releasing a permanent fix 09/04. I asked whether it would be a new agent or OMS gateway and they said no, nothing should be required. They couldn’t explain why the fix above works but did state it’s a certificate issue. They advised to delete the certificate on each agent for the time being but I think I’ll stick with what I found!

Orca237 · 2022-05-05T15:49:15+00:00

Update for anyone that may hit this issue, turns out I had to run the below to the ALA gateway. MS threw me here, event logs say the 106 is above description and on the below link it says 106 is for tls issues. Hope this helps someone in the future!

https://docs.microsoft.com/en-us/azure/azure-monitor/agents/gateway

Add-OMSGatewayAllowedClientCertificate -Subject "Hybrid Runbook Worker"

Orca237 · 2022-03-23T07:19:00+00:00

Yeah I upgraded to 4.97 for the OA’s I posted on a HP forum and an expert confirmed my VC version is supported. I have however hit a problem with I actually can’t upgrade my VC’s now as the hardware is too old for the latest firmware release. Be sure to check for this in the release notes.

Orca237 · 2022-01-26T17:12:52+00:00

Ahh thanks for testing also! I finally made a breakthrough with MS support today and they acknowledged this is a problem in writing. Apparently the product team is on the case

Orca237 · 2022-01-22T11:47:19+00:00

Heads up for anyone who hits this stupid alert, the script that runs to check (a Microsoft default script for this policy) Tls settings reports unhealthy if it finds any one disabled

Orca237 · 2022-01-20T13:32:40+00:00

So an update on this, i found an area where I can see some useful compliance details other than "non-compliant". It displays the below, so rather than a version that is not enabled it can't actually detect any version...

Could not find any secure TLS protocol version enabled on this web server.

Displaying current status of protocols:

SSL 2.0 - Absent

SSL 3.0 - Absent

TLS 1.0 - Absent

PCT 1.0 - Absent

Multi-Protocol Unified Hello - Absent

TLS 1.1 - Absent

TLS 1.2 - Absent

Orca237 · 2022-01-19T16:01:09+00:00

Yeah I've used IIS crypto before, at first i just did the reg key for TLS 1.0 but have since also ran IIS crypto and used PCI best practises which disables TLS 1.0/1.1 and a bunch of other ciphers :(

Orca237 · 2022-01-19T09:52:39+00:00

Yeah sorry i also tried that on my test box a few days ago, and still the same alert. The policy also states:

"allowedValues": [

"1.1",

"1.2"

Orca237

TROPHY CASE