With any luck, you'll be able to specify that with CIDR notation (something like 2001:db8:beef:f00d::/64), if you can't specify hostnames. Note that IPv6 support will be coming soon. If you can specify IP/mask, that's second best: For the US farm, you can use 69.25.78.0/24. " Port ranges were not changed during this work. The more info we receive the easier it is for us to identify and fix individual issues.Also see Report checklist at bottom of page log file if available, and/or the windows event from the windows event viewer, along with a description of what you were doing when it happened such as session type, car and track, configuration files, dxdiag.exe text outputs, etc. To help us to identify each unique issue we require the information specific to the "application error" or "memory error". All crashes are not the same just because they happened in iRacing and the application was terminated due to accessing an incorrect memory address.
What differentiates them are the exception code, exception offset, address accessed. Essentially all crashes are "application errors" and "memory errors". Got which error? There seems to be some confusion about windows error reporting. Win+R > "eventvwr" > Windows Logs > Application > Look for "Error" > Copy report from general tab For my reference, from FAQ for windows 7:.
0 kommentar(er)
