wraith70
-
Posts
165 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by wraith70
-
-
Ok. So I deleted the file from UnitPayloads folder.
My P-47 is saved with an empty payload in ME. In mission. I choose my custom payload with 4s delay. I shows up with the default 0s fuze delay.
BUT, If P-47 is saved with the 4s delay fuze in ME, in mission, It shows up as 4s delay.
So in conclusion, in mission, with an empty payload, and choosing the custom payload with 4s delayed fuze, the fuzing shows up as 0s
Hope this makes sense. Attached is the file again
-
-
Hi Flappie,
I've included screenshots to demonstrate.
'ME Custom Loadout.jpg' shows that my fuse is set and saved to 4s in ME.'Mission Custom Loadout.jpg' shows when I select the same loadout, it defaults to the 0s fuse delay.
Note that I marked my custom loadouts with an asterisk.
Clearly it's not be saved to use in mission.
-
In mission editor, I created a custom cayload for the P-47D.
I select 3x AN-M64 and I set the fuzing to the 4s fuze (can't remember the name).
After saving this loadout, I go to the mission, select the newly created loadout, but when I check the fuzing, it goes back to the default 1s fuzing.
Fuzing doesn't get saved with the payload.
-Wraith
-
45 degree release angle. I wait 5 seconds after the cue stops flashing, pull my 4Gs and I hit my targets all the time. Thanks
EDIT:
Ok. After some testing at different altitudes, It seems that below 1000 feet, I'm successful with a 30 degree release angle.
Above 1000 feet a 45 degree release angle works fine for me
-
1
-
-
A cool way of illumination - by Suntsag
-
1
-
-
End of 2022 and still can't destroy a bridge on the Channel map.
I've tried with explosions, AI P-47, myself and no joy.
-
1
-
-
On 10/28/2022 at 2:20 PM, TOW69 said:
I've been on DCS for years and loved it!!
Lately when I launch DCS with VR I can get to the hanger, however the DCS launch page never comes up.
I just installed 2.8 today, issue was already a problem
Just updated Steam VR
Just installed the latest Nvidia Drivers dated 10/25/2022
I update the 3D shader within Nvidia to 10GB as the support page recommends
Any Help would be greatly appreciated
Updated with dcs log
Update 2 I used the --force_disable_VR to force into windows mode and all I get is a black screen
Something similar was happening to me. I had a program files MOD that was breaking DCS.
Remove any mods you may have and try again.
-
This is sweet! Thanks so much.
Going to try this out with a Huey calling out arty attacks on enemy positions.
-
16 hours ago, Elf1606688794 said:
I tried the mouse scroll wheel and it made me zoom in, that's in addition to showing the ruler.
I just meant press the wheel button, don't scroll. Once pressed, hold and move the mouse around.
-
For a quick ruler, just press and hold the mouse scroll wheel button if you have one and move your mouse to a location.
-
12 hours ago, toutenglisse said:
Yes, I attached a .miz example with P51D and 50°C coolant temp.
The data needed for that are located in mainpanel_init.lua ( \DCS World OpenBeta\Mods\aircraft\P-51D\Cockpit\Scripts ) :
Coolant_Temperature = CreateGauge() Coolant_Temperature.arg_number = 22 Coolant_Temperature.input = {-80, 150} Coolant_Temperature.output = {0, 1} Coolant_Temperature.controller = controllers.Coolant_Temperature
Just wondering why in the trigger you set the Min at 0.56?
-
1 hour ago, warford said:
Hi
I have tried the same procedure and can not ripple two missiles ;-(
Make sure you are using the LAU-117 launcher for your Mavericks. Doesn't work with LAU-88.
-
Not sure it's a bug or if I'm doing something wrong. Tracking moving ground targets to attack with Mavericks.
I enter A/G mode. Mavericks are ON. Switch to WPN page
Switch from GM to GMT mode. Reduce the MAP brightness. I see my moving targets.
Switch from Mav. VIS mode to PRE mode, and the GMT mode seems to reset and I can no longer see any moving targets.
Please see attached track file
-
On 11/7/2021 at 8:09 PM, Crptalk said:
Coordinates are displayed on the FCR when you have a target track or in FRZ.
With SOI on the FCR press 7 on the ICP to bring up the markpoint page on the DED and TMS up to create a markpoint at the current FCR cursor position then press "0" to make it the active steerpoint. Remember to CZ to remove any slews afterwards.
SPI is displayed on the HSI so you can slew the FCR to move SPI to where you want it on the HSI then make a markpoint there.
I didn't realize the Markpoint DED page was working. I'm only able to make a Markpoint using the A/G radar with FCR
-
Bump. Still can't land on the helipad
-
Very jittery in VR for me too...is it necessary?? I haven't seen any difference if I align or not
-
I've been trying to align the HMCS In VR.
Very jittery. I can get through COARSE...at least I can get it to say aligned. AZ/EL and Roll, not too sure.
How are you VR guys doing it. Is it even necessary on cold start?
-Wraith
-
On 10/12/2021 at 5:24 PM, Pizzicato said:
Something else that always trips up DCS scripting newbies is that DCS doesn't automatically reload LUA files that are loaded via the Run Script or Do Script File commands. This means you can find yourself making a ton of changes to a file... and then seeing absolutely no change in the mission. The brute force way of addressing this is by going back to the Run Script or Do Script File commands and reselecting the LUA file via the file browser... but that's really horrible, and really error prone.
The better solution is to use the Do Script command and just insert the following line of LUA:
dofile("C:/<...path to the folder...>/MyLuaFile.lua")
This ensures that the LUA file is always reloaded and refreshed every time you run the mission. Hope that helps.
This works for mission testing. Just remember when you make your mission available to others, that you need to load the actual lua into the mission.
-Wraith
-
1
-
-
Not sure if this is a map specific bug or and AI bug, but a Third Reich halftrack drives into the harbor when fired upon.
Attached is a track.
-Wraith
-
14 hours ago, Dannyvandelft said:
Make sure you fine tune the Steerpoint with the TGP before launching the JSOW. Mine were missing too, and that was because the Steerpoint it uses in PRE mode is either slightly off target, or way up in altitude, or a combination of both. And that causes the JSOW to explode in the wrong spot/altitude and the ammunition drifts off target. Climb to an altitude where you can comfortably see the target through the TGP, slew it onto your target, then fire the JSOW when you're in JIZ range (giggidy) and watch the carnage.
Sent from my SM-G960U using Tapatalk
Steerpoint altitude is important
-
I'm flying the Huey with a 2060 and Rift-S with no issues. No stuttering at all.
-
In Mission editor, check the button on the bottom right isn't pressed..."Historical List of Units"
-
Good observation, I'm curious to know myself.
Custom Payload - Delayed fuze setting not saving
in Mission Editor Bugs
Posted
This still appears to be an issue. Adding and removing bombs will modify the "Saved Games\DCS\MissionEditor\UnitPayloads\P-47D-40.lua file, but changing the nose or tail fuzing does not write the changes to the above mentioned LUA file.
-Wraith