-
Posts
38 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LittleNose
-
Performance issue after looking the F10 map
LittleNose replied to Colos1357's topic in Game Performance Bugs
I agree, it would be nice to have this as an option in setting somewhere. -
Maybe just my iPad, but it seems all the image links are already broken in your link
- 16 replies
-
- bomb fuze
- bombs fuze
-
(and 2 more)
Tagged with:
-
DCS crash issues with the MOOSE 'MarkupToAllFreeForm'
LittleNose replied to LittleNose's topic in Game Crash
Yes, I’d already tried the tips from the log analyzer. Not sure why you think I shouldn’t update with a new log when a patch had been put out? I suspect you meant someone else? It would be helpful if you tried the miz file and lua script that Apple attached in the second message of this thread. For me the mission runs fine if I comment out the single line of the lua script with markuptoallfreeform in it, but crashes every time when looking at the F10 map is that line is not commented out. -
DCS crash issues with the MOOSE 'MarkupToAllFreeForm'
LittleNose replied to LittleNose's topic in Game Crash
Tested with today's hotfix, same symptoms - crashing to desktop upon looking at map (F10) dcs.log -
DCS crash issues with the MOOSE 'MarkupToAllFreeForm'
LittleNose replied to LittleNose's topic in Game Crash
Attached log for the issue reported above. dcs.log -
Is there any more information on what changed with this part of the update? Fixed: Trigger.action.markupToAll only shades in freeform shapes if drawn clockwise. Thanks to the Closed Beta Team! Since the patch, I've been having DCS crash issues with the MOOSE 'MarkupToAllFreeForm' command which I believe works through the DCS markupToAll function.
-
Which flight model should I use?
LittleNose replied to gachatar's topic in UH-1H Paradise Lost Campaign
Artao, you're not alone, I'm not a fan of the new Huey model either. I suspect that there are many more that feel this way too, otherwise I doubt the option to use the old flight model would be there. Love the ambiance of this campaign -
Missing section of road at intersection. Not having this road junction at this location causes a very long detour for ground units travelling on road.
-
I too suffer with this, and I’ve had to drop my terrain texture quality to low, and use the VR Hanger mod to avoid the FPS crash.
-
George AI and AGM-114L Lasing and Fail to Fire Problems
LittleNose replied to GeoS72's topic in Bugs and Problems
Been lurking a while on this subject, as I have also come across this issue with George not firing the Hellfires when within parameters. -
Yes, some information would be good to enable getting strarted with these. Ideally I'd like to see what the fuse settings for each of the weapons shoudl be in order to make them operate as they did pre-patch. This would be a nice base line to make changes from. I'm finding CBU87's and 97's pretty useless on default fuse settings, and I'm not even getting them on target at the moment.
- 16 replies
-
- bomb fuze
- bombs fuze
-
(and 2 more)
Tagged with:
-
This happened to me for the first time today... has anyone else expereinced it lately ?
-
unable to reproduce CTD when adding FCR & Using TADS Video Feed
LittleNose replied to Nightmare22's topic in Bugs and Problems
Finding this same issue with crashing on selection of TADS on the left MFD. MP server, fly F16, switch to Apache, hot start, no FCR, rearm with L type hellfires -
resolved DCS Authorization Failed - 400?
LittleNose replied to HC_Official's topic in Payment and Activation
I've had it a few times today.. I just try again in 5-10 mins, and eventually it works. Seems a bit random -
For anyone else that may in future come across this, the script is now working when I comment out the line ["livery_id"]=list[i]:GetTemplate()["livery_id"] Thanks to MartinCo for the help with this.
-
If it helps, this is the error message I'm getting in the log file: 2023-06-08 11:06:49.987 INFO SCRIPTING (Main): Error in timer function: [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:12474: attempt to index field '?' (a nil value) 2023-06-08 11:06:49.987 INFO SCRIPTING (Main): stack traceback: [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:22632: in function <[string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:22629> [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:12474: in function 'GetGroupTemplate' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:49754: in function 'GetTemplate' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:56065: in function 'GetTemplate' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00006B20.lua"]:200: in function 'IteratorFunction' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:23848: in function 'co' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:23864: in function 'Schedule' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:23878: in function 'ForEach' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:24675: in function 'ForEachGroupAlive' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00006B20.lua"]:189: in function <[string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00006B20.lua"]:188> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:22685: in function <[string "C:\Users\User1\AppData\Local\Temp\DCS.openbeta\/~mis00004746.lua"]:22621>
-
I’ve been trying to get persistence working, and am getting close while using this script. The script is running with the following observations: The save file is updating. I can restart the mission and it loads the save file correctly with the new unit status showing correctly. However, after the ‘restart’ the save file no longer updates. Has anyone else seen this situation and know how to deal with it?
-
I'm trying to replicate the axis controls on the ABRIS. The way that the input controls are set up, it's duration of input that controls how far the cursor moves on the screen (default keyboard command is 7 & 8). This is contrary to the way that the clickable cockpit works. As in you can turn the dial with a mouse movement, and the cursor moves respectively fast or slow. Would it be possible to add in an incremental axis command to the controls options that would work with an encoder type dial and thus be able to create a similar type control for the ABRIS Axis?