New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An-22 Cock, the... well, the update. #986
Comments
I actually don't usually use SQL to directly interface with the DB, so if you just dump a list of DBIDs and the datapoints/values to which you want them changed (like you were doing before) that will fit better into my workflow. (It also makes it easier for me to incorporate all our super sekrit hidden DB tables.) |
Oh dang! 😃
Well, here or maybe in the FAQ, if you could post an example of how you
would yourself fill your ideal report, that could clarify things once for
all.
Just trying to make it as smooth and efficient as possible here.
Thanks for interacting so openly by the way Ethan. It's not always a given.
Cheers
Le lun. 25 avr. 2022 à 07:03, Ethan Hermanson ***@***.***> a
écrit :
… I actually don't usually use SQL to directly interface with the DB, so if
you just dump a list of DBIDs and the datapoints/values to which you want
them changed that will fit better into my workflow.
—
Reply to this email directly, view it on GitHub
<#986 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIQT2XIPLVKZIDBKKZ7DEZ3VGYRRXANCNFSM5UHDP5IA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Fixed 494. I actually had a grand old time using your SQL for the DataAircraft edits. It's only once it starts to get into loadouts, components (mounts, sensors, etc.), etc. that the SQL begins to break down: the working DB is ridiculously complex, and it's honestly just easier to use Access queries rather than SQL for subcomponents since you otherwise have to INNER JOIN the whole damn DB together before you can do anything. (And as mentioned, you guys don't have all the tables you need to do that. You don't want all the tables you need to do that. Trust me.) With DBIDs, I can treat them as "raw" data and do whatever I need. With SQL, if it doesn't work out of the box, I need to first untangle the SQL to get the data into a usable format. I do miss the little task checkboxes though. Those were very convenient for marking my place if the workflow got interrupted! |
This is the only time they let me out of the DB dungeon. |
Just to mention that source number 2 actually is "Butowski, P. (2016). Russia's warplanes: Russian-made military aircraft and helicopters today. Volume 2.", not "Butowski, P. (2017). Russia's air-launched weapons: Russian-made aircraft ordnance today.". Obviously. |
DB Selector
DB3K
Affected DBID(s)
Summary of Changes
UPDATE DataAircraft2345
250 tons max weight comes from a 1966 project, confusingly also named An-22A that didn't get through.
Take-off/Landing Distance is borderline 2004, the figures I have are 1460/1040 m. Your call.
UPDATE DataAircraftFuel23
DataFuel.ID 15 is made of Aviation Fuel x 96000
UPDATE DataLoadout23 (and COPY)
Cargo hold is 33.4 x 4.4 m large, ramp included
20 tons is the weight limit for dropped cargo. Same as for the An-124 by the way.
I'm on the fence with ranges. Source 2 says with Full payload = 3700 km (1998 nm) and Full fuel 9500 km (5130 nm). Source 3 says with Full payload = 5000 km (2700 nm) and Full fuel 11 000 km (5940 nm). I trust source 2 more, it's a long difference, though.
DataAircraftMounts23 DELETE
There's no defensive 23 mm tail gun on that aircraft. The only known armament would be flare bombs.
DataAircraftSensors23 DELETE
Nor there's a Generic Tail Gun Director [TV Camera]
Note : please let me know if formatting the request in quasi SQL actually help. When i'll be done with course, I'll post proper SQL request ^^
Sources
Footnotes
Review and Editing of Unit Descriptions - Page 7 - Matrix Games Forums ↩
Butowski, P. (2016). Russia's warplanes: Russian-made military aircraft and helicopters today. Volume 2. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7
Gordon, E., Komissarov, S., & Komissarov, D. (2004). Antonov's heavy transports: The An-22, An-124/225, and An-70. Hinckley: Midland. ↩ ↩2 ↩3 ↩4 ↩5 ↩6
Sky Pacific Air Services – Antonov brochure(PDF) ↩
[ANTONOV gliders and airplanes - AN−22 ↩
The text was updated successfully, but these errors were encountered: