Schurem's Phight Club (2024-15-09)

I shall slap you with my glove sir…

Got plenty slappin’ tonight. Woof. Rusty. Like I never did this dance in my life. Constantly at too great AoA and still flubbing shots. Not as badly as before the CPU/RAM upgrade tho.

Lots of pancakes from pulling too much AoA, different story for the WWII aircraft of course. Probably a bit too much of pulling too hard rather than waiting for a better opportunity, leading to a lot of snapshots that sometimes connected. That 109 vs F-16 almost became an incredibly embarrassing story! It does illustrate how careful one has to watch their energy state and AoA.

1 Like

Thanks for hosting that Schurem - plenty of interesting dogfighting took place I can see.

This is about the best I did in the FW-190A8…Maico has also landed his P-47.

The Jeff also took a bit of a kicking but I managed to get it down with some of the wing gone on this occasion…success. Unfortunately was unable to turn the loss of weight and drag into an advantage on this occasion!

3 Likes

Oh! what great fun! This was some incredible fun. Sorry I had to run out. I am paying today for the late night (I’m at GMT+3) but will have a smile on my face ALL DAY. Finnally I got some Jug stick time against real people. YAY!
Thanks to @schurem for hosting and to @MigBuster for putting up with my bad flying. @Franze had to talk me through some basic stuff in the Falcon as I have not entered its pit on over a month. In the end I was lost but my own batteries were low too. Still I had a blast.
Cant wait for next time.

1 Like

I may be able to host again tonight. The memory errors I had yesterday evening apparently were cured by setting the bios to last known good. I may miss out on a couple megahertz, but at least I’ll be able to put down the mega hurts :japanese_goblin:

Edit: Nope. Aint happening. DCS repair conks out with access violations and stuff. F!

2 Likes

Can you give more detailed info on what’s going on? Might be a solution out there.

Im standing by on Discord

I’m sat in the lorry with my PC 400 odd miles away anyway and I’m taking the kids to legoland this weekend, possibly be able to play Sunday night though bud

G:\DCS World\bin\DCS_updater.exe
C0000005 ACCESS_VIOLATION at 4ECB0170 00:00000000
00000000 00000000 0000:00000000
4ECB0170 F67EB870 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4EC9B873 F67EB8A0 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4EC9A624 F67EB8F0 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4EC9949D F67EB920 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4EC98255 F67EBE50 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4E7302DD F67EC720 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4E72F507 F67EC750 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4E77C424 F67EC790 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4ECDC675 F67EC7E0 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4EC96700 F67EC810 0000:00000000 G:\DCS World\bin\DCS_updater.exe
4EC8F66C F67EC8C0 0000:00000000 G:\DCS World\bin\DCS_updater.exe
DBBCF476 F67FEF00 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlCaptureContext2()+4A6

does that help? To me that’s soup. Windows memory test is returning errors. CPU is not hot according to its own sensor. I installed a fresh copy of windows and latest drivers for the chipset, graphics card, etc.

How many sticks of memory? Try pulling one out and seeing if memory tests out.

four

4x8? Try pulling sticks one by one, might be a bad stick.

sheeeit. Again? gah!

If Windows memory is returning an error, that’s the first thing I’d try to eliminate. Check all the sticks and go from there.

Well, here we go again…

Took two out, running the test…

If you can’t find a back stick with say slots 1 & 2, try using slots 3 & 4 and see. Motherboard shouldn’t care too much, despite the manuals stating preferred order. Would help identify bad stick vs. bad slot.

Let’s go female dogs! Fight clubs’ back on the schedule!

Tomorrow from 1800ish Zulu! Be there or be square.

1 Like

Yay!! Square I shall not be!!

1 Like

Might be square, might be triangle.

1 Like