Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

1 Follower

About US103_Tobin

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have a totally great direction that the devs should go. Throw away the entire last DM update and go back to what we had before. Sure, it may not be as "advanced". But everything sure seemed fine up until then.... Same with regard to GLOC.... Next up: screw up the gunnery? Please no.... These things they are doing must take up a lot of man-hours, and it doesn't generate any new revenue....does it? Please just make new planes instead, (which you can charge money for) and as far as fixing goes, concentrate on things that people are actually complaining about, such as visibility distance or anomalies, etc. That will not only make your customers happy, but make your company money, as far as I can tell. As for RoF, it's not meant to be a solution or development....only a substitute to take the place of what we've (hopefully temporarily) lost. BTW, RoF went through much of this same stuff before it reached the stage of "no more updates". Disclaimer: These opinions are totally my own and do not in any way reflect the official attitude of JG1.
  2. When you encountered the crash; In what game mode (MP/QMB/campaign/scenario); In what mission; What did you do before the crash; What happened in the mission before the crash; Additional info you think is relevant to the crash. 1) During mission / session sortie, from a few minutes in, to as much as over an hour in. 2) MP and QMB (so far) 3) J5 MP server various Arras map missions, and QMB Arras map continuing 1 vs 1. 4) Just flying around looking for enemies, not engaged in any fights specifically 5) Nothing noticeable, maybe a slight hesitation, then CTD. 6) Don't know if this would happen in other Great Battles series; I only fly FC the vast majority of the time, so might not be specific to FC. Sometimes takes a long time to occur. Recently uninstalled and reinstalled entire game series in order to try to cure CTDs; but CTD's continue. Games installed: BoS, BoM, BoK, FC, BoB Windows 10 64-bit, ver. 1903 Intel i7-5930 K 3.5 GHz (6-core) MSI X99S MB 16 GB DDR4 RAM nVidia GTX 1080, 8 GB GDDR5, + ASUS ROG 34" 3440 x 1440 monitor @ 100 Hz, G-Sync enabled Samsung 950 Pro M.2 SSD main drive, PCIe x4 (32 GB/sec) nVidia driver version: 441.20 Windows Event viewer error report (typical for this crash): Log Name: Application Source: Application Error Date: 12/4/2019 2:03:11 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: MSI-X99S Description: Faulting application name: Il-2.exe, version:, time stamp: 0x5ddc197a Faulting module name: VCRUNTIME140.dll, version: 14.15.26706.0, time stamp: 0x5b3efc77 Exception code: 0xc0000005 Fault offset: 0x000000000000c2ae Faulting process id: 0x48c4 Faulting application start time: 0x01d5aad1dc0c4920 Faulting application path: C:\Program Files (x86)\1C Game Studios\IL-2 Sturmovik Great Battles\bin\game\Il-2.exe Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Report Id: aec0881a-e8e9-46c7-bf68-10d1e76e53f3 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-12-04T19:03:11.852647700Z" /> <EventRecordID>2411</EventRecordID> <Channel>Application</Channel> <Computer>MSI-X99S</Computer> <Security /> </System> <EventData> <Data>Il-2.exe</Data> <Data></Data> <Data>5ddc197a</Data> <Data>VCRUNTIME140.dll</Data> <Data>14.15.26706.0</Data> <Data>5b3efc77</Data> <Data>c0000005</Data> <Data>000000000000c2ae</Data> <Data>48c4</Data> <Data>01d5aad1dc0c4920</Data> <Data>C:\Program Files (x86)\1C Game Studios\IL-2 Sturmovik Great Battles\bin\game\Il-2.exe</Data> <Data>C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll</Data> <Data>aec0881a-e8e9-46c7-bf68-10d1e76e53f3</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
  3. Your Indian head is facing the wrong way. He is running away from the action instead of heading into it. You need an "L" and "R" on your plane, like me. 😅
  4. That's a tough one....the feature itself is pretty cool; but if there is no way to limit it specifically to low or muddy areas on a map instead of an entire map, or if there is no way to give control to a mission designer for where those areas are, then it should be eliminated entirely. Especially with regard to placing airfields, it should be recognized that those would be (and were) improved through drainage and surfacing that renders them usable as such, in the first place.
  5. I don't pretend to understand the limitations; I only ask. BUT....If you allow the Aldis, and then (if it is your preference) de-select it....does it not go back to the DEFAULT configuration? Considering if you had your home view set up for that....would it not be easy to simply de-select the Aldis and then be at default? If you disallow the Aldis, it's IMPOSSIBLE to use it. But if you make it an option, is it not possible to use it, OR....deselct it and then end up with the default config? I stand to be corrected. I think it is important to define what is accepted as the "standard" gun sight. IMHO, that would have to mean whatever sight that you can see if you have NO modifications selected; and in many (if not most) cases, that is actually the best gun sight (or at least the basis) for each plane. So, in my own humble assumptions, I would assume you could see either the the Aldis....or if deselected, the "standard" home view gun sight. In any case, it would not be the optional mod of the "iron" sight, which is just another mod option. Please accept my apologies for my own ignorance. If this is really that big of a limitation, I blame the devs, not you. S!
  6. Hear him. I am actually very surprised that the ratio was one in 5,000 rounds; that seems pretty optimistic. From reading it seems that being actually shot down by flak was almost unheard of; although having bursts near you was very common. In most cases, you might come back with holes in your wings, or even be wounded; and of course, there are the actual shoot-downs recorded. But those would have to be the proverbial "golden BB" hits that just can't be accepted on any repetitive basis in normal events. This is an argument that probably goes back for a LONG way. But the basic concept of flak batteries being concentrated in specific areas, can't really be argued with. Let us stick to reality, an not use such things as tools to obtain any specific goals. In that respect, I thank the makers of B.S. It has provided me with a feeling for realism (flak included) that seems quite like what the reality was, based on statistics and accounts. Keep up the good work! S!
  7. The thing to know about the S.E.5a and Aldis, is that if you use the Aldis, your default home view is centered on that (I assume). Therefore, if the Aldis is disallowed, your default home view will be centered on the ring that the Aldis is mounted in. This is still workable....for those not wanting to alter their original home view. Is that that big of deal? Not on that plane. But if it's on a plane like the SPAD XIII, where the standard gun sight view is different than the Aldis view, then yeah, if any of your Ins/Home/Del/End/Pg Up/Pg Dn keys is mapped to some other function, like TIR, and maybe your view change speeds are too fast for accurate setting without altering them temporarily, it becomes a big deal. I request that the Aldis be available as a modification on the Entente planes, whatever that takes. It can always be de-selected, if not wanted. But it can't be selected, if disallowed on the server side. This is not a mod that has any real advantage; it is just an option. Please enable that. S! and great work!
  8. Lol, at least you're the only person who can SAY that they prefer Entente 😅
  • Create New...