heclak

Those rivets and panel lines are huge. Have you considered toning down on your normal maps?

I suggest having a chat with your coders first. It is a decision that literally determines your first lines of code.

Do you have any specs for the module yet? SFM or EFM Custom avionics or Su-25 or FC3 Clickable or non-clickable cockpit

There's a simpler method? I forgot to mention when i use wsTypeOfWeapon = {4, 15, 47, WSTYPE_PLACEHOLDER} and load mission editor, I guess a bunch of errors. Looks like the wsTypeOfWeapon errored out trying to convert the string to a type number. It seems to only happen for CAT_PODS for me. I'm still trying to trace the stack. [16124] 2019-04-03 23:44:30.434 DEBUG LuaGUI: GUI Error: [string "./Scripts/Database/db_main.lua"]:9: bad argument #5 to 'format' (number expected, got string) [16124] GUI debug.traceback: stack traceback: [16124] [C]: ? [16124] [C]: in function 'format' [16124] [string "./Scripts/Database/db_main.lua"]:9: in function 'wsTypeToString' [16124] [string "Scripts/Database/db_weapons.lua"]:187: in function 'collect' [16124] [string "Scripts/Database/db_weapons.lua"]:207: in function 'collect_available_weapon_resources_wstype' [16124] [string "Scripts/Database/db_weapons.lua"]:220: in function 'collect_available_weapon_resources' [16124] [string "./MissionEditor/modules/me_mission.lua"]:7111: in function 'fillWarehouse' [16124] [string "./MissionEditor/modules/me_mission.lua"]:7133: in function 'createAirportEquipment' [16124] [string "./MissionEditor/modules/me_mission.lua"]:1864: in function 'createMapElements' [16124] [string "./MissionEditor/modules/me_map_window.lua"]:547: in function 'createMap' [16124] [string "./MissionEditor/modules/me_map_window.lua"]:3452: in function 'show' [16124] [string "./MissionEditor/modules/me_autobriefing.lua"]:745: in function 'func' [16124] [string "./MissionEditor/modules/me_wait_screen.lua"]:72: in function 'updater' [16124] [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> [16124] stack traceback: I was using "Point" as I checked in model editor for the name of the connector on the aero-3b model, shouldn't that be the case? I noticed you kept referring to it as LAU7_SHAPE, I checked DCS and I couldn't find an existing model named LAU7. Are you thinking I've already modelled a LAU-7? I'm trying to use the exist aero-3b shape in DCS.

I wouldn’t keep my hopes up....

I would love to do a "functioning" walleye unfortunately guided weapons are just not possible without the SDK telling us how to code it. And it's probably not possible via Lua code too. So our hands are tied.

Haha. Unfortunately, it's just a visual treat. Rest assured other features are being worked on as well. I just committed some new code for some new systems as well. Working on the ACMI pod is a 3D exercise for me.

Still having trouble attaching my custom model on an adapter. My current code is shown below with some comments. -- ACMI POD local pods_data = { ["AN-95"] = { name = "AN/APX-95", mass = "10", ShapeName = "an_apx_95", wsType = {4, 15, 47, 108}, Cx = 0.0019, picture = "ais-pod-t50.png"}, } local function LAU7(CLSID, element) local variant = pods_data[element] local var_mass = variant.mass or 85.5 local data = { category = CAT_PODS, CLSID = CLSID, Picture = variant.picture, displayName = "LAU-7 "..variant.name, wsTypeOfWeapon = variant.wsType, attribute = {wsType_Weapon,wsType_GContainer,wsType_Support,WSTYPE_PLACEHOLDER}, -- no model loaded -- attribute = {4,4,32,50}, -- T-50 loads with pylon -- attribute = {4,4,32,111}, -- T-50 loads with pylon -- attribute = {4,4,32,WSTYPE_PLACEHOLDER}, -- T-50 loads with pylon Cx_pil = variant.Cx, Count = 1, Weight = 15 + var_mass, Elements = { { ShapeName = "aero-3b", IsAdapter = true }, { ShapeName = variant.ShapeName, connector_name = "Point"} } } declare_loadout(data) end LAU7("{AN/APX-95}", "AN-95") I think the issue here is having to use declare_weapon() to declare my acmi pod before being able to attach it to the adaptor. Unfortunately, it looks like it might not be possible as looking in db_mods.lua shows this. This would cause issues as the add_shape_table() isn't called when declaring a CAT_PODS. function declare_weapon(tbl) ... elseif tbl.category == CAT_FUEL_TANKS or tbl.category == CAT_PODS then -- nothing todo ... end I might spend some time looking further into the DCS code but my hopes are not high. The T-50 pod is coded via the ContainerTable.sht and third-party pods are not attached via adapters. So maybe that feature just doesn't yet exist.

Hmmm... That looks rather close to what I tried but using {4,15,47,108} which is the exact type for the T-50 pod kept calling up the T-50 shape instead of the one I've defined. And using WSTYPE_PLACEHOLDER for the wsTypeOfWeapon definition keeps throwing an error as wsTypeOfWeapon doesn't seem to have a stringToInt function. I'll give it another try again tonight. Fingers crossed.

Hi dFlow, If you still have those files (ld_0.edm and ld_1.edm) in your A-4 installation then one of two possibilities are true: 1) You are running an old version of the A-4E. This specific ic issue was fixed two releases ago. You’ll know that you’re running an older version if your cockpit gauge lighting are still white. Please do an upgrade as you’re missing out on a large number of new features and systems. 2) Your upgrade process was performed incorrectly. Updates to the A-4 require deleting the currently installed A-4E folder and placing the fresh copy in its place. This is the only way for us to delete old files that are no longer required/causing problems. Please delete your current folder and replace it with the latest v1.3 install. Please let me know if you have other issues with the module.

Thank you for your feedback on the install instructions. I'll look into updating the install instructions for better clarity. This is an issue in the DCS World engine that was introduced in an OpenBeta patch in February. This affects all SFM aircraft (including the A-4E and MB-3339) and makes then unusable from a ground start. Carrier and air starts are not affected. https://forums.eagle.ru/showthread.php?t=232390 ED had pushed that bug into the stable branch thus it is also affecting stable release users. It has been fixed in the OpenBeta for almost a month now but ED has been holding off pushing the code to the Stable release due to other bugs and CTD related to the Hornet and F-14. We were told the Stable release will be updated in the next few days. I am glad you are finally able to enjoy the aircraft. Congratulations on your landings.

I've already logged this issue in our issue tracker some time ago. I think its a matter of when. But do note that its already on the list. https://github.com/Merker6/community-a4e-c/issues/100

I’ve coded in the bindings for the APC not too long ago. Will be included in the next update. As for the update text, that makes a lot of sense. Especially since there’s number of keybindings added for the next update. I’ll see what I can come up with. Thank you for your compliments and suggestions.

I just checked the latest OB update 2.5.4.29167 which was released today. SFM bugs are still there.

I'm sorry to hear about your difficulties in using Google Drive. In case you ever need to download another file from Google Drive, here are some instructions that I found online. The image is of Google Docs but the text instructions are accurate. If you are unsuccessful with these instructions, you may be using an unsupported/outdated browser. It is important to use an updated browser for personal security reasons. I would recommend Google Chrome but if you want to avoid Google products you can consider Mozilla Firefox or Opera as well.

Hmmm.. I have not update my install to the latest beta. Can someone else on the latest data corroborate if it is indeed broken on the latest beta?

Here's how it looks in modelviewer and the sim. I'm still having some trouble getting it attached via the LAU-7 due to some missing lua declarations for command pods. I think if I can't work around that code then I might really need to model the LAU-7. (I hope not)

Are you having trouble with Google? How can I help you?

The engine sounds are part of the DCS flight model so you can’t replace them without modding your copy of dcs. An audio overhaul is in progress but I can’t confirm the timeline or scope.

NOW AVAILABLE: Community A-4E-C Mod Yea. Those are not used as the A-4 doesn’t have HUD modes. It doesn’t even have a HUD, it’s just a gunsight. Those keybinds are only for FC3 aircraft as they use simplified systems and controls. Sorry but it was probably left there from testing a long time ago. I’ll remove them in the next patch to avoid confusion.

What are those keys suppose to do? Are they for switching hud modes in FC3?

Ground based ILS isn’t implemented yet. As far as I know. Only the carrier ILS has been implemented thus far.

Yea. That’s the general idea.

Yes you can but it’s more than just a declaration. There’s a chunk of code that needs to be written, much like how bomb racks are used. I’ll write that when I get my model into the sim.

Isn't the LAU-7 already in the game?