Node doesnt paste under the cursor. Seems like it goes to a default global position in the batch schematic. Anyone else get this behaviour?
Linux Centos 7
Flame 2021.1.0.164
Node doesnt paste under the cursor. Seems like it goes to a default global position in the batch schematic. Anyone else get this behaviour?
Linux Centos 7
Flame 2021.1.0.164
Yes
If itās happening consistently record a screen recording of it and submit it to support. They seem to respond much quicker to bug that have a video clip attached, likely because they can more easily be reproduced.
@mtheo Youre right. I turn off broadcast monitor in prefs and the paste function works as expected.
Support, that was a bit of maze. Submitted bug feedback here:
Hi @marky753,
The following link cannot be used to submit defect reports.
You need to open a ticket with our Technical Support team for this.
Best,
Yann
Hi @YannLaforest ,
I went in circles there as I dont have a subscription.
Customer support via chat directed me to the product feedback area.
They opened a case based off of that, so it seems to have reached the right people?
best,
Marcus
Hi Marcus,
Thanks for getting back to me.
I followed up with our Support team, and they have made an exception for your case.
Chat support should not have forwarded you to Product Feedback page to report defects. This is not the right channel to report defects.
We apologize for the confusion.
Best,
Yann
Thanks Yann,
Am I correct in thinking without a subscription I cannot report bugs?
M
Hi Marcus,
Yes,
This is correct.
Defects are reported to Technical Support, and Technical Support assistance is available to users who are on subscription.
Please, let me know if you have any other questions.
Best,
Yann
@marky753 This problem has been fixed in Flame 2021.2 Update.
Aww snap! I love these kinds of posts. Nice one @fredwarren!
Hello,
workaround is to use Ctrl+V hotkey instead of context menu āPasteā.
At least this solved it for me.
I was driving from Rhode Island to Vermont and somewhere in the middle of I-89 there was a deer carcass. I avoided it, and when I got to the state police station in Williston, I reported it. I wasnāt going to be driving that way again, but I wanted to make sure that as few people as possible would have to dodge the same deer carcass.
This should be bug reporting in Flame. I donāt need anyone to fix the bug for me, but Iād like to think thereās a useful way for me to help my fellow travelers.
āsupportā and ābug reportingā should be split. I had a godawful time at the Mill reporting bugs because the first question was always something about my license, which me as a dumbass never hadāitās a near miracle that Iām bothering to report a bug in the middle of production, I definitely donāt have time to call up engineering and see what all this license shit is about. If a lead op at a giant client canāt manage to report bugs easily, what hope does anyone have?
If Iām reporting the bug itās because itās likely to ruin other peoplesā day. Bugs arenāt an issue of, āwell Iām not going to drive my car at all until this deer carcass is removed,ā and shouldnāt be treated as such. By the time any bug gets fixed, Iāve delivered the spot in question.
Iām sure Autodesk doesnāt want all of us ham-fistedly firing off bug reports every six minutes, but I donāt think that will happen. Weāre busy people. If weāre submitting bug reports itās because we want to help.