Game Making & Editing FAQ/Q&A
Below are answers to common questions and problems, or Frequently Asked Questions, that often go unanswered that User Generated Content creators or game developers need answering that haven't been elsewhere. For a full list click here »
April 01, 2017, 05:33:53 PM by kat
When editing a project and video is paused in Corel VideoStudio
, the playback Preview
screen/area displays blurry, pixelated or otherwise poor quality video still images (video Snapshot quality is also affected - "Edit » Take a Snapshot
"). Original or source clips don't appear to be affected by the problem, typically displaying clear of any of the pixelation or poor quality visual artifacts when paused or played (subject to project settings).Solution
Assuming there are no other issues related to hardware (drivers etc.), poor quality video in VideoStudio's preview screen is typically the result of using the applications "Smart Proxy
" feature ("Settings » Smart Proxy Manager » Enable Smart Proxy
" or "Settings » Preferences » Performance
") which reduces project quality to speed up the editing process - to save resources and memory when working with larger HD video files, with "Smart Proxy" enabled, VideoStudio creates low resolution, low quality 'proxy' files to aid the process. When enabled this results in the 'poor quality' video images seen in the Preview screen.
Smart Proxy creates lower resolution working copies of larger source files. These smaller files are called “proxy” files. Using proxy files speeds up editing of high resolution projects (for example, projects that have HDV and AVCHD source files). [VSPx9 manual - pg.59]
To address the problem Smart Proxy needs to be disabled
forcing VideoStudio to process and utilise clips as raw and uncompressed as possible. Once Smart Proxy is disabled Snapshots, images taken of a clip as a still image, also clear up reflecting the original quality of source and/or as determined in "Settings » Project Properties
March 22, 2016, 01:02:03 PM by kat
[image courtesy Corel]Problem
Corel Video Studio (Pro) won't run after Windows Update (For Feb/Mar 2016) has been run. Program also does not respond to being placed in Compatibility or other mode (right-click vstudio.exe, select "Compatibility"). The issue is caused by a number of updates to a Windows sub-system that essentially breaks a link in the necessary chain of events needed by Video Studio (Pro). Problem appears to affect Windows 7, Windows 8/8.1 and Windows 10 to a lesser degree.SolutionA 'HotFix' for Video Studio x7 or above is available from Corel here
For Video Studio x6 or below, or in instances where a HotFix cannot be utilised, try uninstalling the following Windows Update files (important: Corel no longer supports v6
For Video Studio (Pro) x7 and above uninstall 3126587
. For Video Studio x6 or below 3140410
may additionally need to be removed. Be sure to disable or 'hide' removed updates to prevent their re-install on reboot. For Windows 7, 8 and 8.1 updates this may necessitate switching Windows Update to 'manual'.
To see and uninstall Windows 7
- from "Control Panel
" select "Programs
" then under "Programs and Features
" click "View installed updates
To see and uninstall Windows 8/8.1
- from "Control Panel
" select "Programs
" then under "Programs and Features
" select "View installed updates
To see and uninstall Windows 10
- click "Start
", then the "Settings
" icon, then "Update & Security
". On the "Windows Update
" page select "Advanced Options
" bottom of the page, then on "View your update history
" on the following page. Click "Uninstall Updates
" top of the page to remove.
'fix' (which may be removed as a result) is available for Video Studio v6 or v5 users here
. Download "MUIHelper.zip
" and extract the contents. Copy the included file "MUIHelper.dll
" to the root directory of Video Studio (Pro), typically "Program Files/Corel/...
" - this overwrites an existing file of the same name, rename the original to archive it before copying over the new file. Video Studio should now start (note it may also be possible to install the previously removed updates).
February 24, 2016, 04:15:54 AM by kat
Q: What is/does getting "FOX'ed" mean?
A: The term "FOX'ed" is a colloquialism to mean something has been 'taken-down' (often without warning) due to an infringement of Copyright pursuant receipt of Cease-and-Desist Notice. Although C&D Notices have a long history of being issued by Rights holders against others deemed to be misappropriating their Intellectual Property, it wasn't until 20th Century FOX issued a Take-down Notice on a Quake
, Alien Quake
, that the practice became more widely known, and subsequently referred to simply as "FOX'ed" - at the time the Alien Quake mod was capitalizing on the popularity of the "Alien" franchise, Property owned by FOX (primary factor), who were actively working on their own materials (secondary factor).
The Alien Quake project has been discontinued by 20th Century Fox. I received an email on April 11th, 1997, from a 20th Century Fox representative that ordered us to cease all activity. The Alien Quake project was using copyrighted material without permission and this makes Alien Quake an unauthorized and illegal production. Therefore, you are hereby ordered to remove all your Alien Quake files from your computer storage. You must also remove all references to Alien Quake from any WWW pages or internet sites you keep or maintain. All distribution of Alien Quake is illegal and you should know that the Alien Quake team are under obligation to report the name and URL of any distributor to 20th Century Fox. Please let us know if you know the URL of a distributor or potential distributor.
Thank you for your co-operation. [source]
Learn more about Copyright, Fan Art
, DMCA Take-down Notices
, and selling games with GPL'd content
September 17, 2015, 04:05:19 AM by kat
Windows 10 appears to be randomly starting systems that have been shut-down without user input.
When a PC is shut-down from Windows 10 "Power" Start menu option ("Start » Power » Shut-down"), systems may restart on their own without user input (the user pressing the power button) anywhere from 30 minutes to several hours after the action. There may be no immediate or apparent reason(s) or causes for the computer to start-up unassisted.
There are potentially a number of reasons why a computer may boot and start-up unassisted.
If the PC successfully boots into Windows, to find out what initiated the boot call, from the "Command Prompt" ("Start » All apps » Windows System » Command Prompt" (right-click "Run as administrator") type "powercfg -lastwake". This will report the last item to initialise the computer and narrow down the device or service making the call.
Wake on LAN
If nothing is listed using "powercfg - lastwake" check to make sure the system is not set to "Wake on Lan". This may need to be done in both Windows 10 "Device Manager" and the systems BIOS (usually "F2" or "F10" to access on start-up). To access "Device Manager" click "Start » Settings » System » About (bottom-left menu) » Device Manager (bottom-right panel)". In Device Manager click the arrow (">") to the left of "Network adapters" to access the available hardware, right-click each entry in turn, select "Properties" and in their respective "Power Management" settings check that "Allow this device to wake the computer" is DISABLED (NO checkbox).
Additionally (and depending on availability, optionally), when checking the PCIe Lan properties (settings associated with a hardwired connection to the PC and not the Wireless device) click "Advanced" and scroll down the options shown to "Wake on Magic Packet"; set the "Value:" to "Disabled". Similarly for "Wake on pattern match"; set it to "Disabled". This essentially turns off 'wake' calls received over Lan.
If the above fail it may be Windows 10 "Fast Boot" ("Fast start-up") feature design is causing the issue (may also applicable to Windows 8.1). With this enabled when a system is shut-down from the Power menu options it does not fully power-off the machine but instead goes into a state similar to "Hibernation" (as opposed to "Sleep" mode) where certain features, services and devices are kept alive in memory to speed to the boot process - from a 'cold boot', all system devices have to be initialised which can take some time to do, "Fast Boot" relieves this by keeping some services in memory requiring fewer to be started on boot, thus reducing boot time. For "Fast Boot" to work, PC's are shut-down but not completely powered-off (so memory can remain active). This 'state' may result in systems randomly booting up without user input or prompting.
The "Fast Boot" ("Fast start-up") feature is part of Windows 10 "Power & sleep" settings and can be disabled (admin rights required). To access click "Start » Settings » System » Power & sleep (left menu)" then under "Related Settings" to the right click "Additional power settings". When "Power Options" opens click "Choose what the power buttons do" on the left then at the top of the page click "Change settings that are currently unavailable" (admin rights required). Scroll to the bottom of the page and under "Shut-down settings" disable "Turn on fast start-up (recommended)" (no checkbox).
Windows Update Reboots
It's also possible that apparent random system reboots are the result of Windows 10 automatically rebooting on schedule or after downloading and installing updates. Depending on the options set this cannot be fully disabled as Windows 10 (currently) downloads and installs updates automatically, rebooting from which can be delayed but not completely disabled (as is possible with Windows 7). To check, click "Settings » Update & security » Advanced options".
July 12, 2015, 02:21:06 AM by kat
The location of the "Start Menu" folder in Windows moves from version to version. It's essentially a protected 'User' location hidden from general access, the contents of which are generated based on the users actions (what software or applications are loaded and need to start when Windows loads).
To edit its contents the folder itself needs to be unhidden and unprotected. To do that open up Windows Explorer
("Start » Accessories » Windows Explorer
") and do the following;
- With Windows Explorer open, click "Tools" then on "Folder Options..." ("Tools » Folder Options...").
- In the pop-up window that appears, click "View" to display the 'view options' for folders in Windows.
- Mid-way down the page is the "Advanced settings:" windowed area - it lists a series of options accompanied with check-boxes - find "Hide protected operating system files (Recommended)" and click the check box to deactivate that options - clears the checkbox.
- A "Warning" will appear. Click "Yes" to agree to turning OFF this feature.
Hidden files will then be visible and available for editing. Once done adjusting the Start Menu follow the same procedure but click the "Hide....
" checkbox to reactivate the option,
hiding system files again.Start Folder location
The Start Folder is usually located in the "User
" directory of the "C:\
" drive where the operating systems is installed, typically;
This would generally means the Start Folder being in the following location;
[user name] » AppData » Roaming » Microsoft » Windows » Start Menu
Or using the actual file path as;
C:\Users\[user name]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Start Menu\
Note that editing Start Menu item directly by accessing the folder in Windows Explorer may cause issues with the system Registry which keeps track of where everything it located or the functionality of features.ResourcesFor help finding Blenders "Scripts" folder click here