If I posted an error log, can you guys assist with fixing it. Here is the info below.

DDSCF Error Log
-------------
Date: 6/20/2018 8:34:02 PM
Source: mscorlib
Message: Exception of type 'System.OutOfMemoryException' was thrown.
Stack Trace: at System.Security.PermissionSet.AddPermissionImpl(IPermission perm)
at System.Security.FrameSecurityDescriptor.CreateSingletonSet(IPermission perm)
at System.Security.CodeAccessSecurityEngine.Assert(CodeAccessPermission cap, StackCrawlMark& stackMark)
at System.Security.CodeAccessPermission.Assert()
at System.Windows.Forms.Control.WmGetObject(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Thanks,

Coach Pop
-----------------------------------------------------------------

Im also having an Error when simming a week when he comes to CPU recruiting. Maybe we have the same problem

Ill have to defer to Brooks on this one

Any news on this topic? Getting depressed with an entire week without the game haha

I haven't heard anything yet

I think I found the reason for this. The cpu recruiting is getting stuck in a loop trying to update recruiting points on a recruit that has already been offered a scholarship. Working on trying to find a workaround.

So the workaround is to go into the team that causes things to get stuck and manually assign their scholarships. This isn't a bug I've noticed before since normally we have plenty of targets for teams to choose from. For some reason in your file there aren't enough targets for some teams so it keeps hitting the same player over and over. I was able to get past South Florida, but then it stuck again on Rice, so I fixed them and then it got stuck on UTEP, then UTSA.

The fact that this is failing on teams in the south is odd... did you do a custom recruit file or any other mods?

So I would go to a team, adjust them, then save, then try simming... if it gets stuck on another team kill the game, and repeat the manual recruiting on that team... and repeat. That should allow you to get past this point in the game. I can't tell at this point if it's a fluke due to the way the recruiting class got generated or a more widespread issue. It may be it happens just this one time.