Archived Forum Post
Index of archived forum posts
Question:
Archived Forum PostQuestion:
I have been unsuccessful at getting past sp_OACreate under SqlServer 2012. The same sproc works on a SqlServer 2008 box.
EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT results in -2147221005 for @hr.
Callig get error: EXEC @HR = sp_OAGetErrorInfo @crypt, @Source OUT, @Description OUT;
results in @Description being "Invalid class string".
I have checked the registry, the clsids are there. I even edited permission on crypt2 and crypt2.1 adding full control to everyone. I also verified the DLL's folder has everyone read/exec permissions.
I am at a loss here.
See the online reference documentation for the correct strings to pass to sp_OACreate. See http://www.chilkatsoft.com/refdoc/xChilkatCrypt2Ref.html
🛠️ Update Released: 4.2.2 Flapping Wings Fix We just shipped a targeted update to fix the erratic bird behavior.
In firmware terms, the 4.2.2 protocol expects a 180-degree out-of-phase flapping pattern (like a real bird). When the system mistakenly shifts to an in-phase pattern, the wings "clap" at mid-stroke, creating destructive interference. The fix requires recalibrating the phase offset to exactly —a value empirically derived from pigeon flight dynamics. 4.2.2 Flapping Wings Fix
This function triggers when the user pushes a key down. You want the bird to change its wing position immediately. 🛠️ Update Released: 4
【HOW TO: Live2d】Wings flap physics tutorial - YoshinoArt The fix requires recalibrating the phase offset to
The fix required a simple adjustment to our state priority logic. ❌ Old Priority Logic if (isFlying) SetAnimation("Flap"); Use code with caution. Copied to clipboard New Priority Logic
In computer graphics, "flapping" is often achieved not through complex rotation, but by rapidly switching between two static images: one with the wings up ( upWing ) and one with the wings down ( downWing ). By default, one wing is set to visible = True while the other is visible = False . The Step-by-Step Fix
It is so that a future version of the ActiveX can co-exist with older versions. You've heard of DLL hell, right? The current naming of "Chilkat_9_5_0." has not changed for several YEARS. Eventually, Chilkat will do a major update to rid itself of all deprecated methods and make long-needed changes which break backward compatibility. When doing so, the name will change -- this will make it so that new programs can use the new version WITHOUT breaking existing older applications.
What about 9.4.x? Did it use the Chilkat.Crypt2 naming? If so, is there a download for it?