-
Posts
67 -
Joined
-
Last visited
About Cooler07
- Birthday 01/01/1900
Personal Information
-
Flight Simulators
A lot
-
Location
TX
-
Interests
A lot
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
IFLOLS and Landing Area Lights Not Visible For Case III
Cooler07 replied to Lspect's topic in Bugs and Problems
Correction boat heading between 345 and 355, inbound final bearing 335 to 345, the best is inbound bearing of 340 degrees so boat heading 355 degrees. -
IFLOLS and Landing Area Lights Not Visible For Case III
Cooler07 replied to Lspect's topic in Bugs and Problems
Edit your carrier so it's heading between 335 to 345 degrees and you will have the ball and the light will be brighter. It's been reported ED and they are on it. -
I didn't think about direction great find and can confirm all lights work if bearing is 335 to 345 give or take a few degrees. even if its a new map all around!
-
Can't help with F-14 deck crew problem, but as for the IFLOS and if at night the Deck runway lighting, I posted in supercarrier main thread (carrier lighting) about making new map with carrier and having no lights at all, and as reported someone said the IFLOS was backwards. At night the deck lighting is also backwards. F9 pan to bow at night. I edited and older training map and added fog and the deck crew active and the IFLOS and Deck lighting work perfect. Try and older map made before last few patches or download the map I have in main tread and edit it for F-14's etc and see what happens. Good luck.
-
Hi all, as with others here I also have made new map with carrier and all the setups TCN,ILS,ACLS, LINK4 deck crew fog night and didn't meatball or carrier lights. So I used and old training map SC, Deck crew,fog, and all the other setting as above. And on a case 3 all the lights were bright and meatball at 1.5 miles everything looked great even the underdeck lighting at back of boat was off so the vertical lineup lights were easy to see. I'm not sure why it works with old mission map and not the new map. Also when doing case 3 when you call (inbound) the carrier turns on meatball and then you call establish then commencing the carrier turns on deck lighting and red taxi lighting. It works perfectly on the old map NOT new maps?????? Don't ask me how! I'll attach the mission TCN 71 ILS 20 LINK4 332 night time 1/2 mile in fog you can adjust in editor. there are player aircraft in air and on carrier plus 4 IA F-18's inbound, I've also tried it without AI and the same with AI lights working. I've tested in SP and MP both 2d and vr pimax 8kx. And all works great. So if someone would try this mission out and see what you get it might work for you also. Thanks for your time. FOG_ACLS_F18_NIGHT_OPS_VERSION_1.0.miz
-
Sorry for got to post mission for anyone. CAT_1_STROBE_JTAC.TEST_MAP_77.miz
-
Check this video out.
-
This is a quick vid showing JTAC control and Strobe position marking. It's a bit low res and this is my first video for DCS. But it does show how I got JTAC with voice commands only and DEMO strobes.
-
-
Thanks for info!
-
Question: F4 and Jester As per the manual Jester can make call outs for waypoints as in IP,TGT,HB in 20,15,2 miles from waypoint. I’ve tried setting this up in mission editor, and have noticed in the F4 edit part like radios, load out, there’s a tab for Navigation Target Points. Does anyone know how to make this work for Jester to make these call outs? Or is this not available yet in F4 module? Thanks
-
Same here like the new NVG’s, but have to say that I still can’t see my own laser and have also noticed that I can see jtac laser without NVG’s on dark night. This is in single player MT. Going to try test in multiplayer today. I have some screen shots but there hard to see in VR. Maybe someone else can test. System info windows 10 pro I9 9900ks 5G ROG z390 MB 64 ddr4 3800 Corsair dominator Asus ROG 4090 oc Pimax 8kx normal FOV PD 1.5 DCS PD set to .5 OpenXR for Pimax DCS OB MT
-
Mike Force Team started following Cooler07
-
I get the 2 disconnect warnings 10500 and 10600 when i first start pitool also and then after about 30 or 40 seconds it loads up. I'm guessing you have firmware V2.1.255.299? I'm trying to find more info but it's hit and miss up here on forum.
-
Not sure what to tell you I've been running this version for sometime. Sorry
-
I hate to put these up and yes I have lucked out with the DCS God’s System info windows 10 pro I9 9900ks 5G ROG z390 MB 64 ddr4 3800 Corsair dominator Asus ROG 4090 oc Pimax 8kx normal FOV PD 1.5 DCS PD set to .5 OpenXR for Pimax DCS OB MT Default setting Openxr Tool kit but for turbo mode that’s the only thing I changed. could NOT get screen shot of openxr menu. Info in pictures. FPS between 70-90 if I run shadows flat it's 90+ The screen shots are not the best but i can see everything good for 61 year eyes!