Tags

- Minor fixes and renaming in the demos that allow to record and display online headset data (along with collision data) - this feature was introduced in February 2025.
	See Demos in ...\PTVR_Researchers\Python_Scripts\Demos\Tracking_of_hand_head_or_gaze\   
	See Documentation section [Recording handcontroller, headset, etc.](@ref recordingHandcontrollerEtc) 

- Textbox : improvements of vertical and horizontal alignments (along with improvements in Text's DocString).
	See Demo: ...\PTVR_Researchers\Python_Scripts\Demos\Text\alignment_of_text.py
   
- Renaming of several parameters in the the3DWorld class (along with improvements in its DocString) :
	output_headset replaced with output_headset_data_and_collisions   
	output_gaze replaced with output_gaze_data_and_collisions  
	output_hand_controller replaced with output_hand_controller_data_and_collisions  
	eyetracking replaced with activate_eyetracking

- minor fixes	
- Improvement of PTVR Documentation concerning the use of Vive or Quest/Oculus Systems.

- PTVR is now compatible with [Meta Quest](https://www.meta.com/) 1, 2 and 3 headsets (in addition to previous compatibility with HTC Vive Pro series headsets). 
- The few requirements allowing PTVR to work with the Quest headsets are presented in the ['VR device Setup: Meta Quest' section](@ref setupQuestHMD). 
- PTVR will continue the integration of other headsets thanks to [OpenXR](https://en.wikipedia.org/wiki/OpenXR). This will be done based on users' feedback.

- Improved color management of FlatScreens.
- Added a two-color reticle.

- PTVR is now compatible with Unity 2022.
- Beta testers are welcome to tell us if they encounter bugs with this new
version.

- Improved the Sprite object to display several hundred of them without affecting the program performance

- New Coordinate System (CS) : Azimuth and Elevation   
    See Demo in ...\PTVR_Researchers\Python_Scripts\Demos\Positions\    
    3.0_create_object_in_azimuth_elevation_coord.py       
	or Demo in ...\PTVR_Researchers\Python_Scripts\Pedagogical_tools\Maths\         
   azimuth_elevation_CS.py    
	

- set_spherical_coordinates () is deprecated: use set_perimetric_coordinates() instead.   
	see [cheatsheet on Objects' position](@ref specifyPositionCheatSheet)
- set_spherical_coordinates_on_screen () is deprecated: use set_perimetric_coordinates_on_screen() instead.   
	see [cheatsheet on Objects' position](@ref specifyPositionCheatSheet)

- a new directory has been created: /Pedagogical_tools/Maths
	See for ex. rotations_in_global_and_local_cartesian_CS.py   

- It is now possible to record in a file the position and orientation of the **headset** with the same logic as for the handcontroller. Notably, the recorded files allow the user to get coordinates of the collision between the headset (or handcontroller) direction and a Tangent Screen (TS).   
	See Demos in ...\PTVR_Researchers\Python_Scripts\Demos\Tracking_of_hand_head_or_gaze\   
	See Documentation section [Recording handcontroller, headset, etc.](@ref recordingHandcontrollerEtc)    

- New script illustrating a recent "augmented vision" experiment  
    See Demos in ...\PTVR_Researchers\Python_Scripts\Experiments\Augmented_Vision\  
    2025_IEEEVR_paper.py   
	    https://hal.science/hal-04918641

- small bug corrected in visual_search.py

- The structure and the names of the  free asset bundles stored in https://files.inria.fr/ptvr have been tidied up.

- It is now possible to record in a file the position and orientation of the handcontroller.  
	See Documentation section [Recording handcontroller, headset, etc.](@ref recordingHandcontrollerEtc)

- About creating objects imported from asset bundles using CustomObject().

	In PTVR releases prior to 1.1.3, the asset bundles that were necessary to create CustomObjects could be stored on any directory of your PC (with the paths of these directories defined in your scripts).	
	From this version on, to simplify the handling of paths, you will have to store all your asset bundles in a directory called:
	"/Asset_bundles". 
	In addition, this directory will have to be at the same level as the "\PTVR_Researchers" directory.
	
	For instance, if you installed PTVR such that it was in the following directory:
	C:\Nancy\PTVR_Researchers
	then the directory containing ALL your asset bundles will now have to be in:
	C:\Nancy\Asset_bundles.
	
	Another change is that the free asset bundles stored in https://files.inria.fr/ptvr are now organized in directories to help you retrieve easily the asset bundles you need (e.g. for a certain demo). As this directory structure is not the same as in previous PTVR versions, the current release contains a link to a zip file (Asset_bundles_for_PTVR_releases_prior_to_1_1_3.zip) containing all the asset bundles that you need if you run scripts developed with PTVR releases prior to 1.1.3. Note that you will always have access to this zip file in https://files.inria.fr/ptvr.	

	Another related change concerns the new 'asset_bundle_name' parameter when you import an asset bundle with CustomObject(). See the example code below:   

		my_character = CustomObject(
		asset_bundle_name = "humans_cartoons",
		asset_to_load = "Assets/Prefabs/Boy.prefab"
		)

- New important parameter in CustomObject()
You can now type 'display_animations = True' to see in the headset above the CustomObject (Asset bundle) created what are the available animations associated with this object.  
Illustrated in these 2 demos:
...\PTVR_Researchers\Python_Scripts\Demos\Assets_to_import_into_PTVR\      
   20_animate_rabbit_asset.py and  
30_boy_asset_w_walk_and_run_animations.py  

- RENAMING  
(you'll have to replace these names if you used them previously in some of your scripts)
'Sprite' has been replaced with 'Image' in the 5 following objects:    
ReticleSpriteFromDrawing -> ReticleImageFromDrawing   
ScotomaSpriteFromDrawing -> ScotomaImageFromDrawing   
SpriteFromDrawing -> ImageFromDrawing   
SpriteFromLoading -> ImageFromLoading  
SpriteToContingentCursor ->  ImageToContingentCursor   
The reason is that the previous names containing 'Sprite' gave the wrong impression that these objects were creating or using PTVR [SPRITE objects](@ref spriteObjects).

- Minor hotfixes and documentation changes.
- Some objects related to movements (e.g. Translate) that were defined in :
	"...\PTVR_Researchers\PTVR\Data\Callback.py" 
are now defined in:
	"...\PTVR_Researchers\PTVR\Data\Callbacks\MovementCallback.py"
Thus the following line of code will induce an error:
	import PTVR.Data.Callback
so that you should now write:
	import PTVR.Data.Callbacks.MovementCallback

- New demos in ...\PTVR_Researchers\Python_Scripts\Demos\Assets_to_import_into_PTVR.
They illustrate some new features when importing and animating Assets (characters, animals, objects, landscape, cities, vehicles, ...).

- New demos in ...\PTVR_Researchers\Python_Scripts\Demos\Global_Variables
They illustrate some of the many uses of the"global variable", a very important new feature which potentiates the possibilities offered by callbacks.

- Improved Documentation (see User Manual -> Pointing at an object) and Docstrings for flat Cursors (reticles, scotomas, ...) and Pointing events.
- Improved documentation for Sprites (see User Manual -> Visual Objects -> Sprites or Flat 2D objects.

- Big Improvements of the Flat Cursor Objects aka contingent Sprites. These objects allow us notably to create contingent artificial scotomas and reticles (crosshairs). Highly detailed documentation is also now provided. This release corresponds to the publication (end of April) of the PTVR paper "PTVR (Perception Toolbox for Virtual Reality) a software in Python to make virtual reality experiments easier to build and more reproducible." in a special Journal Of Vision issue on Virtual Reality

Improved demos with CustomObject.

- Improved CustomObject class to load assets from an AssetBundle.

- Added CustomObject class to load assets from an AssetBundle.
- Added several demos to use CustomObject.

- Eyetracking bug fixed: gaze_cursor_pointing_with_recording.py works again
- Updated documentation on eyetracking
- MNRead test bug fixed : mnread_vr_experiment.py works again
- Modified .gitignore to include .txt from the MNREAD experiment