Jump to content

GSHWK_Houndstone_Hawk

Members
  • Content Count

    39
  • Joined

  • Last visited

Community Reputation

40 Excellent

About GSHWK_Houndstone_Hawk

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    South West England

Recent Profile Visitors

382 profile views
  1. This is going to be a 'great' Christmas thanks to these guys.
  2. Couldn’t care for the Pacific theatre ... crikey it’s been done in the past so many times but this next venture is a truly fantastic direction and compliments the previous release so well, and with a little imagination from previous aircraft, Battle of Britain in VR can now be a reality ... but the C-47 (clearly the most iconic aircraft of the Normandy invasions) simply HAS to be playable and the map needs a western ‘grey’ to the skies and the English landscape littered with a patchwork-blanket of hedgerow-bordered small fields. It’s an expensive buy so it must be done right but I’ve every confidence that this team ‘will’ pull it off
  3. Amazing skin. Is it available for download anywhere?
  4. Hi. I've just finished doing blocks. Wow what a labour of love that was. Anyway I'll upload them to the original post at the top. **edit** https://www.dropbox.com/s/o73hjfwb2qxy60j/IL-2 Objects Visual Reference Charts v1.01.rar?dl=0
  5. If you use Great Britain and Germany factions it’ll pretty much guarantee a proven working scenario
  6. Hmm. Although I can only comment on the S.E.5 mission as it's the only one I've tried but on discovering the group of Halberstadts not attacking us I went in and hasd a little delve into your mission & sure enough found what I suspected. You've done nothing wrong per say but at present it seems that the WWI coalitions you're using are acting as neutral & are not attacking each other (hence the 'white' icons). Through much trial and error recently I've found that the only coalitions that will attack are USSR, Great Britain & United States (Blue) against Germany (Red). Anything else that will be represented by a non-colour seems to act passively. Maybe a little more presentation & info for the user to feel involved & immersed also but otherwise nice addition.
  7. I received it 10th Oct and it came with the clip that's meant to eliminate the connection issues so I'm guessing it's a v2. Well let's hope you have a successful head set there 😁
  8. It's as I feared. It's the headset and the dreaded cable problems. Both ends (headset & PC) are secured off and in no way being restrained but nothing is stopping the black screening and it's now so frequent it's completely useless as a product. Every time it goes blank I check device manager & sure enough, under Monitors, Windows no longer recognises the headset. Had it for 8 weeks after much careful musing and reading up on the reverb pro. Thought I was going to be one of the lucky ones but wasn't to be. Makes me wonder ... How on earth did they let such a shabby product out the door in the first place. I tried to defend a head set for its painful wearing on the nose, for it's ridiculously heavy and uncomfortable cables at the rear of the head set because I wanted to love it & to enjoy the improved visuals and I would've put up with all the down falls that go with it but it's a useless heap of junk in it's present state. Back to the Oculus Rift (that's gonna be tough on the eyes lol). Thanks for the above replies.
  9. Hi. Anyone else with a Reverb Pro suddenly experiencing constant crash-outs since 4.001b? Headset goes black then cut to desktop and sometimes even causes blue screen and a system restart. It was fine and running lovely and smoothly with better fps etc when 4.001 was released but then it's now crashing all over the place. IL-2 is the only title I play in VR so I can't benchmark it against other titles but it works fine in WMR home. At first thought perhaps it was a SteamVR issue but now I'm not so sure. Most of the time it will blackout and crash shortly after entering the cockpit (between 30 secs to 2 mins usually), sometimes it'll crash out on menu screens (even loading). Since the problems, I 'have' noticed an awful and very uncomfortable 'flickering' during loading (used to be just the SteamVR 'mountains & stars' backdrop but now the mission map stays on screen during loading and flickers like mad. Have to look away. Everything fine again as soon as loading completes. This I've only had since the mini update to 4.001b. *************************************************** My Hardware GPU: GTX 1080 Ti (current driver is 26.21.14.4112) CPU: i9-9900k @ 3.60 GHz (currently running @ 4.97 GHz) PSU: 1000W PSU RAM: 32 GB (3200 MHz DDR4) M/B: Z390-F Gaming motherboard *************************************************** WMR Visual Quality: High resolution: 4320 x 2160 (best quality) Experience options: 90 Hz Input switching: Manually switch using the Windows logo key + Y *************************************************** SteamVR 1.8.20 Reprojection: On Custom resolution: 150% (each eye at 2412x2364) *************************************************** IL-2 v4.001b Main setting: Balanced Screen resolution: 1280x720 UI scale: Auto Shadows quality: Low Mirrors: Simple Distant landscape detail: x2 Horizon draw distance: 40 kmZ Landscape filter: Blurred Grass quality: Normal Clouds quality: Extreme (fps actually seems better on Extreme than High) Target FPS: 100 (near as I could get it to achieve 90) Dynamic resolution factor: Full Antialiasing: 2 Gamma correction: 0.9 Full screen: unchecked Enable VR HMD: checked Multi GPU support: unchecked Vsync: unchecked SSAO: unchecked HDR: unchecked Sharpen: unchecked Use 4k textures: checked Distant buildings: unchecked I've tried different USB ports on my Z390-F m/b inc the red 3.1 inputs as well as the blue. No go. Tried the zip tie trick to better eliminate the cable connection from the back of the headset. This is so so frustrating as I'm longing to enjoy version 4 particularly with the seemingly smoother running and improved fps but this is currently rendering it unplayable and any help or advice would be very welcomed indeed.
  10. Hi. Anyone else with a Reverb Pro suddenly experiencing constant crash-outs since 4.001b? Headset goes black then cut to desktop and sometimes even causes blue screen and a system restart. It was fine and running lovely and smoothly with better fps etc when 4.001 was released but then it's now crashing all over the place. IL-2 is the only title I play in VR so I can't benchmark it against other titles but it works fine in WMR home. At first thought perhaps it was a SteamVR issue but now I'm not so sure. Most of the time it will blackout and crash shortly after entering the cockpit (between 30 secs to 2 mins usually), sometimes it'll crash out on menu screens (even loading). Since the problems, I 'have' noticed an awful and very uncomfortable 'flickering' during loading (used to be just the SteamVR 'mountains & stars' backdrop but now the mission map stays on screen during loading and flickers like mad. Have to look away. Everything fine again as soon as loading completes. This I've only had since the mini update to 4.001b. *************************************************** My Hardware GPU: GTX 1080 Ti (current driver is 26.21.14.4112) CPU: i9-9900k @ 3.60 GHz (currently running @ 4.97 GHz) PSU: 1000W PSU RAM: 32 GB (3200 MHz DDR4) M/B: Z390-F Gaming motherboard *************************************************** WMR Visual Quality: High resolution: 4320 x 2160 (best quality) Experience options: 90 Hz Input switching: Manually switch using the Windows logo key + Y *************************************************** SteamVR 1.8.20 Reprojection: On Custom resolution: 150% (each eye at 2412x2364) *************************************************** IL-2 v4.001b Main setting: Balanced Screen resolution: 1280x720 UI scale: Auto Shadows quality: Low Mirrors: Simple Distant landscape detail: x2 Horizon draw distance: 40 kmZ Landscape filter: Blurred Grass quality: Normal Clouds quality: Extreme (fps actually seems better on Extreme than High) Target FPS: 100 (near as I could get it to achieve 90) Dynamic resolution factor: Full Antialiasing: 2 Gamma correction: 0.9 Full screen: unchecked Enable VR HMD: checked Multi GPU support: unchecked Vsync: unchecked SSAO: unchecked HDR: unchecked Sharpen: unchecked Use 4k textures: checked Distant buildings: unchecked I've tried different USB ports on my Z390-F m/b inc the red 3.1 inputs as well as the blue. No go. Tried the zip tie trick to better eliminate the cable connection from the back of the headset. This is so so frustrating as I'm longing to enjoy version 4 particularly with the seemingly smoother running and improved fps but this is currently rendering it unplayable and any help or advice would be very welcomed indeed.
  11. You're welcome and good luck with the mission building 😉 I'm making them as I go. Each jpeg is 705x488 so a little too large I guess but you're quite welcome to them (If I can find a why to upload them that is)
  12. I've started making these for personal use as I find the pictured examples and country identification etc a little tough-going & thought I'd upload them to here in case anyone else wanted to make use of them. I aim to have reference charts for all things from blocks to buildings etc. ------------------------------------------------------------------------------------------------------------------- **Edit 15/11/19** Version 1.01 link below, now includes all 'Blocks' from BoX series as well as Flying Circus. v1.01 Current Contents BoX 'Artillery' Box 'Blocks' Box 'Ships' Box 'Trains' BoX 'Vehicles' FCV1 'Artillery, Vehicles & Aerostats' FCV1 Blocks https://www.dropbox.com/s/o73hjfwb2qxy60j/IL-2 Objects Visual Reference Charts v1.01.rar?dl=0
  13. Hi. Great MOD. Having huge troubles setting up zoom features though. Whatever I do I cannot get the zoom settings to move 'up' Holding down the zoom (HOME) key whilst repeatedly pressing Left CTL + Page Down I can clearly see the setting having an effect and the view moving 'down' but holding the zoom (HOME) whilst repeatedly pressing Left CTRL + End and absolutely nothing happens at all. I'm not having issues with the Windows ease of access or sticky commands & I've tried different keyboards as well as uninstalling & re installing the mod but nothing seems to make a difference. Any help would be greatly appreciated as I'd love to get a working set of zoom settings that I could save.
  14. JimTM & Gambit sure are a great help for us novices. To get the route to show in mission map I believe you place 'Translator Icons' by your waypoints (name them WP 1, WP 2 etc & in Translator Icon properties, select the ID to 'waypoint')) & you then 'target link' each one to the next, starting and finishing at the home airfield (thus creating a loop). That's how I do it at least. Re. the FC planes to attack each other, it's best to still use the coalitions that actually work (like 'Great Britain', 'Germany' etc)/ I'm not sure if Great Britain WWI, Entente etc are actually recognised and working coalitions yet within the mission editor. I might be wrong but I've so far only managed success in FC mission editor by using 'Germany', 'Great Britain' etc.
×
×
  • Create New...